On Thursday, July 12, 2012 1:37:49 PM UTC+1, Lukas Eder wrote: > > That will depend on the database that you're using. In standard SQL > UPDATE statements, this isn't possible (without writing several SELECT > statements) >
The code base we're using targets Oracle, MySQL and HSQL. We have successfully used the onDuplicateKeyUpdate() portably across all 3 databases, which was a strong reason to use JOOQ :-) So if I understand you correctly, in this particular scenario, there is no portable compile-time JOOQ construct we could use - rather we would have to make the application code dialect aware and construct DB-specific JOOQ objects for each of the databases we support?
