On Tue, Jun 9, 2020 at 9:24 AM Thorsten Schöning <[email protected]> wrote:
> The idea of concurrently using the same JDBC-connection came only > afterwards, when adding reports which don't query the database at all. > Those can be processed multi-threading with reports which do query the > database in theory, but I currently don't know which report accesses > the DB when scheduling those. So it would be great if concurrent > access of JDBC would just work and I don't need to care too much. :-) > But my other suggestion stands. Why have concurrent access to the JDBC Connection when you can have a single process that manages this connection and that can receive messages (possibly async) to hide managing the connection for you? With Oracle, I've done this many times in the past, using AQ as a means for inter-process communication, even across servers, not just across threads... -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO7V31pcaUOTAnvMTDszknKYofRZjS7KHx9f4_b76y8Puw%40mail.gmail.com.
