Hi Lukas, You are the one who deserves thanks. I guess you're making the best decision. It's a short-term sacrifice for a long term gain. I think developers tend to put too much effort on keeping things backward compatible and sometimes that's at the expense of quality at the end of the day. It is a hot debate in the java world, even inside the JDK itself.
Best Le lundi 17 décembre 2012 20:27:03 UTC+1, Lukas Eder a écrit : > > > 1. It is surprising to some users, and thus "voodoo". Voodoo is never > good. > > 2. It is not entirely reliable when extracting bind values from jOOQ, > > thus the original GitHub issue > > https://github.com/jOOQ/jOOQ/issues/2001. Without removing the current > > feature, this issue is hard to fix and it was brought up several times > > on this list. > > 3. Its implementation is a kludge (isNullLiteral()). Removing this > > implementation would greatly improve the code base > > 4. Those few users that might rely on this feature can live with > > writing if / else checks as suggested in this thread. > > 5. jOOQ already supports the DISTINCT predicate (IS [NOT] DISTINCT > > FROM), which is the correct SQL way of doing NULL-agnostic checks > > ... not to forget: > > 6. The current implementation of eq/equal/ne/notEqual is inconsistent > with [NOT] IN, [NOT] BETWEEN, gt/ge/lt/le and various other > predicates. >
