Dear group, Many of you have noticed that jOOQ 3.9 introduced a parser. Its main use-case (for now) is the DDLDatabase [1], which allows for reverse-engineering your DDL scripts rather than connecting to a live database, for the code generator.
But there are a few other use-cases I have in mind in the long run, namely the capability of translating SQL strings between dialects. Imagine this as a Flyway plugin, which allows you to write your migrations only once, and then run them on any database. You can play around with the SQL translation capability on the following website [2]: https://www.jooq.org/translate Or, use the technique mentioned in this blog post [3], where the parser / translator is exposed via the JDBC API, and could be used to migrate your legacy applications, e.g. from Oracle to SQL Server. The continuous improvement of the parser also depends on your feedback. If you could try some really funky SQL queries of your own on the website here [2] and report any issue that you may have encountered either on this list, or on GitHub [4], that would really help boost this exciting new feature! Of course, your other ideas what to do with the parser are very welcome as well. Cheers, Lukas [1] https://www.jooq.org/doc/latest/manual/code-generation/codegen-ddl [2] https://www.jooq.org/translate [3] https://blog.jooq.org/2018/01/12/top-5-hidden-jooq-features [4] https://github.com/jOOQ/jOOQ/issues/new -- 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.
