| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "Jaime Casanova" <systemguards(at)gmail(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Subject: | Re: someone working to add merge? |
| Date: | 2005-11-11 19:07:00 |
| Message-ID: | 5066E5A966339E42AA04BA10BA706AE50A93B1@rodrick.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jaime Casanova Wrote:
> But MERGE isn't REPLACE...
>
> REPLACE will delete old records to insert new ones; MERGE try
> to insert and if the record exists then can UPDATE just a few
> values, maybe incrementing them with a value (all the
> calculation are doing by the MERGE)
That sounds like MySQL's 'INSERT INTO ... ON DUPLICATE KEY UPDATE',
which they recommend over REPLACE anyways.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-11-11 19:07:43 | Re: Multi-table-unique-constraint |
| Previous Message | Peter Eisentraut | 2005-11-11 19:06:35 | Re: someone working to add merge? |