DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	b=UGCt0kNa7cCrg3ZmcvN4qmojnEom/NzZu0xF9EmI1XQlektAPgQVZ1dzLU90szClfY2ywkw0yut5Ta6gvAvznyShCJ9uODMn1t0QVuds5YSLnNygvUMfMzwRzdwkZXMF38Hfa5k/Ez3z+vdGVTaUmTXfEnowumZjXrByHqym97g=
Message-ID: <32207abd0703200211l46acdab7p5a2d68d69ffc5b6c@mail.gmail.com>
Date: Tue, 20 Mar 2007 10:11:41 +0100
From: "remco lengers" <pgsql@lengers.com>
To: pgsql-sql@postgresql.org
Subject: ERROR: duplicate key violates unique constraint
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_130234_20319974.1174381901895"

------=_Part_130234_20319974.1174381901895
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi List,

Its been a while since I worked with databases and I am running into the
following which I have not been able to find the root cause for:

I have the follow SQL statement:

INSERT INTO reference VALUES (DEFAULT,'123','2',1);

Which generates the following error:

"ERROR:  duplicate key violates unique constraint "reference_pkey""

And the table definition looks like:

CREATE TABLE reference (
referencelist_nr serial unique,
reference_text varchar(40) NOT NULL,
reference_type integer NOT NULL,
Topic_Id integer NOT NULL,
PRIMARY KEY (referencelist_nr),
FOREIGN KEY (Topic_Id) REFERENCES Topic (Topic_Id),
FOREIGN KEY (reference_type) REFERENCES reference_type (reference_type_nr)
);

It seems to me for some reason "DEFAULT" doesn't select the next SERIAL.
If I run:

INSERT INTO reference VALUES (14,'123','2',1);

14 being the next free integer it works fine.....

I have been adding data with "COPY" into this table....does that break
something?

Your help/tips/insights are appreciated.

Solaris 10/Postgresql 8.1.4

Regards,

..Remco

------=_Part_130234_20319974.1174381901895
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi List,<br><br>Its been a while since I worked with databases and I am
running into the following which I have not been able to find the root
cause for:<br><br>I have the follow SQL statement:<br><br>INSERT INTO reference VALUES (DEFAULT,&#39;123&#39;,&#39;2&#39;,1);
<br><br>Which generates the following error: <br><br>&quot;ERROR:&nbsp; duplicate key violates unique constraint &quot;reference_pkey&quot;&quot;<br><br>And the table definition looks like:<br><br>CREATE TABLE reference (<br>


referencelist_nr serial unique,&nbsp; 
<br>reference_text varchar(40) NOT NULL, <br>reference_type integer NOT NULL, <br>Topic_Id integer NOT NULL,<br>PRIMARY KEY (referencelist_nr),<br>FOREIGN KEY (Topic_Id) REFERENCES Topic (Topic_Id),<br>FOREIGN KEY (reference_type) REFERENCES reference_type (reference_type_nr)
<br>);<br><br>It seems to me for some reason &quot;DEFAULT&quot; doesn&#39;t select the next SERIAL.<br>If I run: <br><br>INSERT INTO reference VALUES (14,&#39;123&#39;,&#39;2&#39;,1);<br>
<br>14 being the next free integer it works fine.....<br><br>I have been adding data with &quot;COPY&quot; into this table....does that break something?<br><br>Your help/tips/insights are appreciated.<br><br>Solaris 10/Postgresql 
8.1.4<br><br>Regards,<br><span>
<br>..Remco</span>

------=_Part_130234_20319974.1174381901895--