Good. Good things come to those who wait (with answering user group threads) :-)
Cheers Lukas 2013/11/22 Ernest Mishkin <[email protected]> > My apologies. Please ignore this topic - I was misinformed and the "other" > columns are in fact TIMESTAMP. So JOOQ behaves as expected. > > > On Friday, November 22, 2013 9:42:29 AM UTC-5, Ernest Mishkin wrote: >> >> I have a bit of a mystery with JOOQ 3.1.0 generating java.sql.Date >> mappings for *some* DATE columns and java.sql.Timestamp for *other* DATE >> columns (those are in different tables). >> There are no forcedType config entries. >> Is there some tricky logic being applied somewhere in generation code? >> DB is Oracle 10.2 (though I don't think specific version of Oracle plays >> a role). >> >> Thanks! >> > -- 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/groups/opt_out.
