> 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 :-)
Great, good to know! > 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? In this particular case, you can't use jOOQ to translate MERGE or ON DUPLICATE KEY UPDATE syntax to all of your three databases (yet).
