[Sorry if this is a double post.]
Hello all,
[Postgresql 7.4.2]
CREATE TABLE "story" (
"id" int4 NOT NULL,
"title" varchar (100) NOT NULL,
"body" text NOT NULL,
"entryDate" timestamptz NOT NULL,
CONSTRAINT "story_pkey" PRIMARY KEY (id)
);
In the above table why does the query:
UPDATE "story"
SET id = (id + 1500);
fails with:
"ERROR: duplicate key violates unique constraint 'story_pkey'"
(I have 6000 records in the table with "id" spanning from 1 to 6000)
I find this behaviour strange, SQL is a set based language, but
PostgreSQL is acting like is changing the values in sequence.
Can anyone with a better understanding of PostgreSQL explain to me why this
happens?
Are my expectations wrong?
Best regards,
Luis Neves
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
