OK, thanks I'll give that a try. Data-type rewrites are a good workaround. FYI, the link below points to a dead-end: This link works: http://www.jooq.org/doc/3.2/manual/code-generation/data-type-rewrites/
On Friday, February 28, 2014 2:12:27 AM UTC-5, Lukas Eder wrote: > > Hi, > > A SQL TINYINT has 8 bits or 1 byte, so the closest match in the Java world > is java.lang.Byte. We chose wrapper types over primitive types for two > reasons: > > 1. They can be NULL > 2. They work better with the all-present generics in jOOQ's API > > If you're working with *int* variables in your user code, you will have > to turn them into java.lang.Byte manually, through casting and > (auto-)boxing. > > If you prefer to work with java.lang.Integer instead (deferring the risk > of overflow to the database), you can rewrite data types in the code > generator: > http://www.jooq.org/doc/manual/manual/code-generation/data-type-rewrites/ > > Cheers > Lukas > > > 2014-02-27 23:19 GMT+01:00 <[email protected] <javascript:>>: > >> What's the corresponding Java type? Is the expectation that the user cast >> an *int* variable to a *byte*? >> >> 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.
