> On the other hand, this shows that maybe re-writing SQL data types > (without converters) doesn't work reliably at all. jOOQ needs some > sort of type information, when binding variables through the JDBC > API. > If BOOLEAN is the only information available to jOOQ, it cannot > guess that TINYINT (or NUMBER) would be a more suitable type.
In fact there's a whole lot of reasonable encodings. It can be a character data type with an encoding of Y/N (or J/N in German shops, O/N in French shops, 0/1 in C-influenced shops, etc.) For numbers, some encode it as 0/1, others as 0/-1. Not all encodings are reasonable, but all are in use :-) -- 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.
