2014/1/18 sergivs <[email protected]> > Thanks! > > A method like record.insertOnDuplicateKeyUpdate() would imply that all > (non-key) fields should be updated from the given record instance. So it is > not as comprehensive as the other, explicut aporoach, but I think it would > be quite useful in some cases. >
Yes, it would be useful in many cases. It reminds me of H2's MERGE statement, which does precisely that: http://www.h2database.com/html/grammar.html#merge > insertOnDuplicateKeyIgnore() would also be useful. True, that should be added as well, for consistency reasons. I've updated the issue title Cheers Lukas -- 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/groups/opt_out.
