Hello, Excellent news!
Yes, I had a look at the code a while ago before I started using jooq, Connections obtained from datasources were proxied to close automatically, unfortunately that wasn't very suitable for JDBC-style transaction scenarios. I chose to use jooq because I was growing tired of ORMs, frameworks, POJO domain models, 7-layer java cake designs and all those over-engineering practices that are so common in the java world nowadays so I'd like to avoid relying on containers. Of course I can live with Connection based factories but I am not against a nicer way to manage transactions ;-). Thanks for all your work Lukas! Best Le lundi 29 octobre 2012 11:31:29 UTC+1, Lukas Eder a écrit : > > Hi Stéphane, > > > I would have loved to see this one : > > https://github.com/jOOQ/jOOQ/issues/1629 > > Yes, these features will be addressed in jOOQ 3.0. I forgot to mention > this specific one. > > > 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 > > Yes. Also the usage of DataSources along the lines of distributed > transactions (i.e. closing pooled connections after usage) does not > necessarily work well for developers who do not rely on containers. > > I'm hoping to generally improve that area in 3.0 > > Cheers > Lukas >
