Re: [GENERAL] Unique constaint violated without being violated

2008-12-08 Thread Tom Lane
"Richard Broersma" <[EMAIL PROTECTED]> writes: > Does this mean the PostgreSQL supports row-wise updates? When did this > happen? Only sort of ... http://archives.postgresql.org/pgsql-committers/2006-09/msg00021.php I didn't want this applied http://archives.postgresql.org/pgsql-patches/2006-07

Re: [GENERAL] Unique constaint violated without being violated

2008-12-08 Thread Richard Broersma
On Sat, Dec 6, 2008 at 7:36 AM, Merlin Moncure <[EMAIL PROTECTED]> 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_t

Re: [GENERAL] Unique constaint violated without being violated

2008-12-07 Thread Dot Yet
funny!! :) too bad, i also noticed it only after reading Merlin's response :) On Sat, Dec 6, 2008 at 11:12 AM, Sebastian Tennant <[EMAIL PROTECTED]>wrote: > Quoth "Merlin Moncure" <[EMAIL PROTECTED]>: > > It looks to me like you are setting the whole table to the same > > address in the update st

Re: [GENERAL] Unique constaint violated without being violated

2008-12-06 Thread Sebastian Tennant
Quoth "Merlin Moncure" <[EMAIL PROTECTED]>: > 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? > > merlin Doh! Thanks Merlin. I'm so glad it's just

Re: [GENERAL] Unique constaint violated without being violated

2008-12-06 Thread Merlin Moncure
On Sat, Dec 6, 2008 at 10:27 AM, Sebastian Tennant <[EMAIL PROTECTED]> 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_ti