Hi all, On Friday, September 29, 2017 at 2:56:36 PM UTC+2, Lukas Eder wrote: > > That explains why it would be unwise for jOOQ to consider that "length" > information for any type deduction. > > The "global" type conversion mechanism that you could use would be to > create your own general-purpose Binding and use that for every dynamically > created column expression (you'd have to know these columns in advance, > though). > > (sorry for the late reply)
While it might be unwise for JOOQ to do so, I found that in our specific setting, we only use tinyint as a boolean. Therefore I added it to our mapping: <!-- Associate data type rewrites with database columns --> <forcedTypes> <forcedType> <name>BOOLEAN</name> <types>tinyint</types> </forcedType> </forcedTypes> This works for us, might be useful for others so I thought I'd mention it here Groeten, Friso -- 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.
