Null handling is indeed not trivial, but I think this is more relevant for eq/ne than for gt/in - gt(null) should throw an NPE in my opinion, and in(null) should probably translate to IN () ). Leaving it up to the user is a reasonable decision. In my case the column is nullable and I ended up creating a wrapper eqOrIsNull and neOrNotNull to get the behavior I was expecting.
Thanks, Ariel On Thursday, June 26, 2014 2:23:34 AM UTC-4, Lukas Eder wrote: > > A small correction: > > 2014-06-26 8:18 GMT+02:00 Lukas Eder <[email protected] <javascript:>>: > >> - And probably the worst: Query.getSQL() would now render less bind >> values than reported by Query.getParams() and Query.getBindValues(). jOOQ >> could no longer interoperate with other APIs, e.g. Spring's JdbcTemplate. >> > > That might not be correct, in fact, as the behaviour of these methods was > changed with > https://github.com/jOOQ/jOOQ/issues/3131 > -- 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/d/optout.
