Thanks for documenting this, Daniel. While it is correct that you should specify the SQLDialect for best results, there's still a bug hidden in there. The exported data type is SQL Server's INT type, which should work out of the box when re-importing the XML. The point being that there should either be:
- Some standardisation when exporting - Some lenience when importing Probably, standardisation is the cleaner approach. I've registered an issue for this: https://github.com/jOOQ/jOOQ/issues/5741 Thanks again for reporting! Lukas 2016-12-23 19:53 GMT+01:00 Daniel Einspanjer <[email protected] >: > Aha. I was missing the property telling it what dialect to use. This > configuration caused it to use Integer types as expected: > > <database> > <name>org.jooq.util.xml.XMLDatabase</name> > <properties> > <property> > <key>dialect</key> > <value>SQLSERVER</value> > </property> > <property> > <key>xml-file</key> > > > -Daniel > > -- > 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.
