> As I am currently on a business trip, I don't get to run the pre-release > integration tests on a level I would like. So I prefer postponing the > release of 1.5.4 until the weekend. Another reason is that I have recently > gotten very much appreciated feedback and bug reports about things that > might evolve to be major issues. So those issues might also be fixed in > 1.5.4, or in a subsequent patch release. I hope you understand
The feedback I am currently getting is going in a very good direction. With the 1.5 release stream, jOOQ does not yet support multiple inter- dependent schemata. It is only possible to generate code for one schema at a time. But if database artifacts are distributed and connected over multiple schemata, there might be various issues in code generation AND execution. This is a scenario that I have not yet thought about, as the use case I have been using (and testing) jOOQ with so far, was restricted to single, independent schemata. Most databases are not advanced enough to create these scenarios anyway. But with the recent feedback from an Oracle user, jOOQ will push a lot more into the direction of supporting these things and becoming a tool of choice for enterprise developers. That's great news, as I am currently not aware of any competing tool (or "standard", see my discussions about Hibernate, JPA) with the power of supporting SQL as a DSL, source code generation, advanced datatypes, stored procedures AND multiple schemata. I hope you share my enthusiasm for such a tool. Watch out for future releases with even more advanced features. Together we can make jOOQ a tool for excellent integration of Java and SQL. Cheers Lukas
