| From: | "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
| Cc: | "Sebastian Tennant" <sebyte(at)smolny(dot)plus(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unique constaint violated without being violated |
| Date: | 2008-12-08 17:02:34 |
| Message-ID: | 396486430812080902r7b8f8251k53e580b784a77ca2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Dec 6, 2008 at 7:36 AM, Merlin Moncure <mmoncure(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-12-08 17:31:12 | Re: Unique constaint violated without being violated |
| Previous Message | Scott Marlowe | 2008-12-08 15:58:59 | Re: TurnKey PostgreSQL: new installable live CD optimized for easy of use |