Hi Lukas, Thanks for the pointers. I've returned it to the broken state and run with trace enabled, but the statement (with variables bound) is also 'correct' in the log; that is, if I copy and paste that query, it gives the correct result in both Oracle and HSQLDB (I'm not currently targeting any other DBMS). However, the query being executed is still incorrect unless I use the aforementioned workaround.
I'm hesitant to post the query, since I haven't attempted to reduce it to a smallest failing case. If anyone's really interested, I'm happy to, but I'm more concerned with knowing what's really being sent to the database. Oh, to clarify, the db variable is a org.jooq.impl.Factory (though you probably guessed that already). Cheers, Anthony On Friday, January 4, 2013 11:33:34 AM UTC, Lukas Eder wrote: > > ... note that actual bind values are logged in TRACE level > > > 2013/1/4 Lukas Eder <[email protected] <javascript:>> > >> Hi Anthony, >> >> jOOQ logs all queries to your preferred logger in DEBUG level. This is >> documented here: >> http://www.jooq.org/doc/2.6/manual/sql-execution/logging/ >> >> You can also write your own ExecuteListener to hook into jOOQ's execution >> lifecycle: >> http://www.jooq.org/doc/2.6/manual/sql-execution/execute-listeners/ >> >> Cheers >> Lukas >> >
