Hello Lukas, one point about the generic Map<Object, Object> on all Scope Types, that you have mentioned...
im currently constructing a new Jooq Configuration and DSLContext for every incoming Request / Thread in my blocking quarkus application, and had planned to remove this requirement and to share the Jooq Configuration and DSLContext and inject it everywhere instead of constructing it many times, like explained in: https://www.jooq.org/doc/latest/manual/sql-building/dsl-context/thread-safety/ When i now use the generic Map<Object, Object> via "configuration.data(x, y)", like you mentioned it seems that i may run into Thread-Safety issues? - if thread A changed configuration.data(), will thread B also see this changed configuration.data() in a multi-threading environment? If yes, then: - a) maybe the "data()" function for Scope-specific data may not be the right way to do what i need (passing around thread-specific context-objects in a multi-threaded environment) - b) i need to keep Constructing new DSLContext for every Thread to keep them separated, so i can use "data()" in an isolated manner. best regards, Bernd -- 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/4b932ac7-5b39-4d85-a4e1-ab4eb6ab072cn%40googlegroups.com.
