Hi > I'd like to avoid this because of the unstable JDBC API: With every release, Sun adds some new methods which breaks code that extends JDBC interfaces :-(
With Java 8's defender methods / extension methods, these problems should be gone. > So a new interface which just has two methods (borrowConnection() and returnConnection()) would move the unstable part into jOOQ hiding it from all your consumers. This looks like the existing JDBC API to me. Re-implementing that might be a bad idea in terms of usability and compatibility. Note, there is also another thread on this group dealing with the possibility of adding new types for JDBC abstraction with the purpose of simplifying exception handling. Cheers Lukas
