> I'll have to review this. Postgres can handle nulls well. It shouldn't > be necessary to inline null as a literal. I'll further investigate > this. It might actually be a bug: > > https://sourceforge.net/apps/trac/jooq/ticket/1128
I can confirm that this is a "bug" or rather a flaw originating from early times of jOOQ, when the API was not yet very stable and it was difficult to bind null correctly in databases such as DB2 and Derby. This bug originates from #172: http://sourceforge.net/apps/trac/jooq/ticket/172 Some background information can be found on Stack Overflow, too: http://stackoverflow.com/questions/4504658/cast-null-in-db2-sql-statements With jOOQ-Spring integrations, the current NULL-behaviour is rather weird. Thanks to Andrea for reporting this. I'll see that it can be fixed in jOOQ 2.0.4 Cheers Lukas
