Hi Sander, >> What about if jOOQ just always calls provideFor() before every query >> execution, so you can run those (and additional) checks yourself? You >> (client code) know more about what's a good Connection and what is >> not. If I get a new Configuration through provideFor(), I'll use that. >> Otherwise, the existing Configuration will have to do. And we'll leave >> the original calls to provideFor() on deserialisation of a Connection. >> I somehow feel, this will be the cleanest solution. What do you think? > > That sounds like an excellent solution!
Feel free to check up on that solution using the latest SNAPSHOT: https://oss.sonatype.org/content/repositories/snapshots/org/jooq/ Cheers Lukas
