Interesting, thanks for your update, Erik. I'm not sure if I caught the message: Does jOOQ still have this issue today? jOOQ doesn't use any of those JDBC extension types, including CachedRowSetImpl. Also, jOOQ doesn't use ResultSetMetaData, unless when using "plain SQL" queries. The code generator directly reverse engineers the dictionary views, such that type information is hard-wired to the generated schema classes...
2016-09-26 16:23 GMT+02:00 <[email protected]>: > Old thread, but relevant update on this--the problem in a more general > sense is that MySQL's Java driver is upgrading the actual java type on an > unsigned value to account for the higher range of values, BUT it is not > changing the SQL type reported. As such, it will convert an Unsigned > Integer to Long, but the SQL type remains type 4, or per Java to SQL > standard "Integer". This results in issues where the SQL type is > interpreted, which includes in the Java class CachedRowSetImpl. As such, > this isn't just a JOOQ issue to resolve, but may touch many different > packages that use the CachedRowSetImpl, which includes Spring I believe. > > On Tuesday, May 10, 2011 at 4:38:42 PM UTC-4, FractalizeR wrote: >> >> MySQL has UNSIGNED modifier, which makes following type unsigned. Jooq >> generator maps such types still to int, which is signed in Java. >> Technically binary representation of both is still 4 bytes, but if >> converted to string, you might get different values. >> >> Is that ok? >> > -- > 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. > -- 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.
