Re: Unique constaint violated without being violated - Mailing list pgsql-general

From Richard Broersma
Subject Re: Unique constaint violated without being violated
Date
Msg-id 396486430812080902r7b8f8251k53e580b784a77ca2@mail.gmail.com
Whole thread Raw
In response to Re: Unique constaint violated without being violated  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: Unique constaint violated without being violated  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Sat, Dec 6, 2008 at 7:36 AM, Merlin Moncure <mmoncure@gmail.com> wrote:

>>  itidb=> update joblist set (full_name, email_address, recruiter,
>>  itidb(> subscribed, verified, created_at, updated_at) =
>>  itidb-> ('[name hidden]', '[email address hidden]', false, true
>>  itidb(> true, current_timestamp(0), current_timestamp(0));

> It looks to me like you are setting the whole table to the same
> address in the update statement (no where clause)...so of course you'd
> get the error.  Maybe you want to do an insert statement?

Does this mean the PostgreSQL supports row-wise updates?  When did this happen?


--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: TurnKey PostgreSQL: new installable live CD optimized for easy of use
Next
From: Tom Lane
Date:
Subject: Re: Unique constaint violated without being violated