This documentation is for the unreleased development version of jOOQ. Click on the above version links to get this documentation for a supported version of jOOQ.
Dialect compatibility
Applies to ❌ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
When supporting multiple dialects, there are some dialect specific behaviours that are inconsistent between dialects. This is especially true for NULL values in Oracle.
The following settings govern dialect compatibility behaviour:
-
Settings.renderCoalesceToEmptyStringInConcat: This flag will use COALESCE on all operands of a String concatenation expression in order to turnNULLvalues to'', which is Oracle's more useful, but not standards compliant behaviour. -
Settings.renderNullifEmptyStringForBindValues: This flag wraps string typed bind values in a NULLIF(?, '') expression in order to turn""input values back intoNULL, which is what Oracle does for theVARCHAR2andCLOBdata types, which don't have an empty string representation.
Feedback
Do you have any feedback about this page? We'd love to hear it!