Hi Lukas, I would have loved to see this one : https://github.com/jOOQ/jOOQ/issues/1629
For people not relying on some container for transaction management, it would save a lot of code. I often find myself testing autocommit state to know whether I should start and commit/rollback a new transaction or just let the caller take care of it. Best Le vendredi 26 octobre 2012 15:31:22 UTC+2, Lukas Eder a écrit : > > Dear community, > > The recently released version 2.6.0 is probably the last minor release > on the 2.x version stream. The time has come to move on to the next > major step, jOOQ 3.0. Important features of the 3.0 major release will > include: > > - Improved Record type-safety through row value expressions > - Improved Factory / Configuration API through clean separation of > query building and query execution > - Improved thread-safety (hopefully) > - Improved code generator, which should be more extensible (possibly > based on Aaron Digulla's suggestions) > - A cleaner "classic" API (as opposed to the DSL API) > - Experimentation with more advanced JPA annotations support when > mapping Record into POJOs > - Experimentation with Scala 2.10 Macros > - Removal of all deprecated things > - Lots of minor improvements to the API > > For more details about what is currently being planned, please > consider the relevant milestone on GitHub: > https://github.com/jOOQ/jOOQ/issues?milestone=17 > > Also, feel free to suggest major improvements that should be > implemented in a major release. Now is the time! > > Do note that if you're building jOOQ directly from GitHub master, you > may find some API instability in the next couple of months. > > This release currently has no due date. I expect to have a first > release candidate ready by the end of December 2012, though > > Cheers > Lukas >
