| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Replaceing records |
| Date: | 2003-09-04 16:10:10 |
| Message-ID: | 1062691810.6781.148.camel@coppola.ecircle.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> You can do
> INSERT INTO tab (...) VALUES (...) ON DUPLICATE KEY UPDATE col=val, ...
This would allow making sure insert won't throw exceptions on unique
constraint violations. Good enough to avoid breaking transactions.
>
> But I'm not sure how convinced the developers are of its usefulness beyond
> satisfying mysql migrations. I've never used mysql and I have seen a few times
> it might have been useful. Not a lot, but a few. And it seems to be a frequent
> question on the mailing list.
If nested transactions is easier to implement, that would be better.
Covers more of the current problems.
Cheers,
Csaba.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera Munoz | 2003-09-04 16:10:16 | Re: [HACKERS] tablelevel and rowlevel locks |
| Previous Message | Andreas Muck | 2003-09-04 16:03:05 | Re: More than 1024 connections from the same c-backend |