| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Jaime Casanova" <systemguards(at)gmail(dot)com> |
| Subject: | Re: someone working to add merge? |
| Date: | 2005-11-11 18:54:00 |
| Message-ID: | 5066E5A966339E42AA04BA10BA706AE50A93AF@rodrick.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane Wrote:
> Surely they require a unique constraint --- else the behavior
> isn't even well defined, is it?
From the mysql manual:
'REPLACE works exactly like INSERT, except that if an old record in the
table has the same value as a new record for a PRIMARY KEY or a UNIQUE
index, the old record is deleted before the new record is inserted. See
Section 13.2.4, "INSERT Syntax".'
... John
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Hansen | 2005-11-11 18:55:42 | Re: someone working to add merge? |
| Previous Message | Tom Lane | 2005-11-11 18:44:57 | Re: someone working to add merge? |