In Oracle, famously, '' IS NULL. jOOQ currently doesn't care about this and just passes along all empty strings or NULL to the JDBC driver directly.

If someone uses jOOQ (e.g. the parser) to migrate from Oracle to PostgreSQL, for example, then it would be useful for jOOQ to turn empty string bind values into NULL instead. A new Settings.bindEmptyStringAsNull flag would enable the feature for all String bind values.

Of course, with ordinary jOOQ usage, a custom Converter or Binding could be used, instead.

There are 2 ways to go about this:

• Settings.bindEmptyStringAsNull works only when executing the query. (See Add Settings.bindEmptyStringAsNull to emulate Oracle behaviour on other RDBMS #16478)
• Settings.renderNullifEmptyStringForBindValues works also when rendering a query. (This issue)

Both are true / false flags, default being false

See also:

• https://groups.google.com/g/jooq-user/c/u4WIVkqvYo4
• Add Settings.bindEmptyStringAsNull to emulate Oracle behaviour on other RDBMS #16478