Hi Lukas, concrete use-case of a 3rd party tool that really relies on jOOQ > providing it with a "dedicated" connection through the > ConnectionProvider API. >
Let's go back to the origins. In our application (the simple version being a fat client deployed on all of our clients' users' computers with direct database access), the contract of getting a connection through our connection providing API is hard: you must release what you acquire and it is reserved. All our integrated tools like our console can get connections from that central place. At any time, even over a remote session with a client when troubleshooting an issue, we can fire the console to log and/or execute statements. This saved us on many occasions, both at development time as well as in production. My goal was to try to ease this firing of the console in the context of JOOQ too. Let's sum up: 1. Is ConnectionProvider a generic way of acquiring connections: No. 2. Does JOOQ provide a centralized/generic way of acquiring dedicated connections: No. Conclusion: it is unclear whether tools have to create their own mechanics to get dedicated connections. Depending on the type of ConnectionProvider, this may or may not be suitable, but using connections when it is not suitable could result in awful corruptions. I originally thought that with little API tweaks maybe users could create a Configuration/ConnectionProvider per target and pass them to JOOQ DSL as well as tools. Too bad! :) Cheers, -Christopher -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
