Thank you very much for reporting, Anthony. Would you mind showing also:
- The DDL of your table - The XML configuration of your code generator It's probably easier to track down the issue with actual code than a description of code... Thanks, Lukas 2017-02-01 0:23 GMT+01:00 Anthony Calce <[email protected]>: > Hello, I have found the following bug (MariaDB): > > - I am forcing type TINYINT to INTEGER > - If I do a customType and forceType on a column (which is TINYINT), > the generator doesn't pick up the converter correctly, and this column is > typed as INTEGER (as per the type forcing rule). > - I have tried setting my converter's type to Byte, Short, and > Integer, and nothing helps. > > This isn't my only column I'm custom typing (so I know I'm doing it > right). It's just the only column with 2 force-type rules. Any ideas on > how to solve this? I can just change the column's type back to INTEGER for > now (this eats up 4x more data though) > > -- > 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.
