Hi Denis, Thank you very much for chiming in on this discussion, and sorry for the delay.
2016-01-12 14:57 GMT+01:00 Denis Miorandi <[email protected]>: 1. code generation: would be great have more options about pojo generation. > I.e. generate json-schema / json of tables or xml/xsd of tables. In some > situations could be nice. That's very interesting. Let me get this right: You're using SQL Server to store and manipulate XML data that is based on registered XSD - correct? So, jOOQ's code generator could, in principle, fetch these XSD, trigger XJC code generation to produce JAXB annotated objects, and register those via the out-of-the-box AbstractXMLasObjectBinding ( http://www.jooq.org/javadoc/latest/org/jooq/impl/AbstractXMLasObjectBinding.html). Am I getting this right? How about JSON, how does that work in SQL Server? Also, could you perhaps show an example of what a runtime use-case for these features would be? 2. something more about xml /xpath /json queries type safeting. I don't > know really how but of course db dependent... Yes, this would be DB dependent, indeed. Looks like we could discuss potential new features in the other thread that you've started here: https://groups.google.com/forum/#!topic/jooq-user/PcYhxv6gWkI Best Regards, Lukas -- 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.
