Group, I'm still not 100% convinced that #2700 should be implemented as suggested: https://github.com/jOOQ/jOOQ/issues/2700
The suggestion is to check if NOT NULL constraints and DEFAULT values are available on any given column, and then change the behaviour of a DAO.insert() method to treat Java nulls as SQL DEFAULTs, instead of SQL NULLs. While this may seem useful in this particular use-case, it seems to me that we're about to open yet another pandora's box of unexpected behaviour. This is why I postpone this fix. There's a valid workaround in most cases, and I better get this completely right. 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.
