PostgresQL does not support MERGE though (http://wiki.postgresql.org/wiki/SQL_MERGE). So I think if one is using PostgresQL one would generally fall back to the exception/update approach. Is that right?
Regards, Raman On Wednesday, June 25, 2014 6:42:00 AM UTC-4, Deven Phillips wrote: > > I have had MANY co-workers and colleagues make that statement about > MySQL... I think it just indicates laziness... Oh well, perhaps I am overly > critical because I am such a huge fan of PostgreSQL.. > > Deven > > On Wednesday, June 25, 2014 4:05:09 AM UTC-4, Lukas Eder wrote: >> >> >> 2014-06-24 18:15 GMT+02:00 Deven Phillips <[email protected]>: >> >>> It always annoys me when people say they MUST use MySQL because it has >>> UPSERT... >>> >> >> People do say that? >> >> >>> UPSERT is STUPID, but implementing that capability using a SQL standard >>> like MERGE is VERY NICE! >>> >> >> I thought so as well :) >> We're also emulating INSERT IGNORE ... using MERGE, in fact. Except that >> the jOOQ syntax is INSERT .. ON DUPLICATE KEY IGNORE >> > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
