Hi Gili, I can see your point. Maybe the Factory itself should hold commit(), rollback(), savepoint() and similar methods, throwing DataAccessException. How have others solved this?
Lukas Am Montag, 11. Juni 2012 schrieb Gili Tzabari <[email protected]>: > Hey Lukas, > > What about committing transactions? If I have to invoke Factory.getConnection().commit() after the JOOQ code I still end up having to catch both DataAccessException and SQLException. Couldn't Factory.getConnection() return a wrapper object? > > Gili > > On Thursday, June 7, 2012 6:04:27 PM UTC-4, Lukas Eder wrote: >> >> Hello, >> >> The true reference for these things is the current Javadoc, for instance: >> http://www.jooq.org/javadoc/latest/org/jooq/Cursor.html#hasNext%28%29 >> >> It looks as though the manual is not up to date. jOOQ should never >> throw a SQLException. I'll fix this in the manual, soon: >> https://sourceforge.net/apps/trac/jooq/ticket/1489 >> >> Thanks for reporting this >> >> Cheers >> Lukas >> >> 2012/6/7 Gili >> > Hi, >> > >> > I'm pretty sure I posted this question recently but I can't find a trace of >> > it so here goes... >> > >> > Looking at http://www.jooq.org/manual-single-page/ I see that some methods >> > throw SQLException while other methods throw DataAccessException. Why do we >> > have both these exceptions? Should JOOQ only throw one? >> > >> > Even if this was fixed, it looks like I'm forced to invoke >> > Factory.getConnection().commit() to commit the transaction. Since >> > factory.getConnection() returns java.sql.Connection, the commit() method >> > throws SQLException again. Shouldn't JOOQ provide a wrapper class that wraps >> > converts all SQLExceptions to DataAccessException? >> > >> > >> > Thanks, >> > Gili >
