Am Donnerstag, 14. Juni 2012 16:04:32 UTC+2 schrieb Lukas Eder: 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. >
Cool :-) Only ... it will be 2018 until I can use that release ... > > 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. > Well, duh. I introduced the API in my code so that my mapper would work with more than a single version of Java (I was supporting 1.4, 5 and 6). But if you only plan to support Java 8, then that's of course not an issue for you. Which means to me that I'll have to fork. I don't mind; I have lots of forks here. It's just frustrating to have to do it because of so few lines of code. Regards, A. Digulla
