Hi Kevin, To my best knowledge, a database "session" corresponds to a JDBC Connection in most RDBMS. This is independent of transactions, as a session can have several transactions. Most Java connection pools are thread bound and will guarantee that any logic from the same thread will receive the same connection (session) again for every request within a transaction. Of course, there are esoteric cases where this isn't true.
Hope this helps, Lukas On Mon, Feb 25, 2019 at 6:56 PM Kevin Embree <[email protected]> wrote: > Thanks for the information, I will look into if that is a better solution. > Postgres 'SET' is defined for a 'Session'. If my DSLContext comes from a > DataSource resource that uses connection pooling. > Can the postgres session change from one transaction to another? > > Thanks for the help, > -Kevin > -- 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/d/optout.
