You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When implementing custom Bindings, users may need to create temporary LOBs or other objects that need to be free()-d after usage. Ideally, these free() calls will take place right before the Connection is closed (i.e. returned to the pool), or when the transaction ends.
The jOOQ Configuration should expose some sort of ResourceManager, that handles these things. jOOQ would then also use this new type internally, instead of the existing ThreadLocal workarounds in DefaultExecuteContext
Moving this to 3.7.0. The newly added #231BlobBinding and ClobBinding implementations can still use the internal DefaultExecuteContext API for registering resources in a ThreadLocal
When implementing custom
Bindings
, users may need to create temporary LOBs or other objects that need to befree()
-d after usage. Ideally, thesefree()
calls will take place right before theConnection
is closed (i.e. returned to the pool), or when the transaction ends.The jOOQ
Configuration
should expose some sort ofResourceManager
, that handles these things. jOOQ would then also use this new type internally, instead of the existingThreadLocal
workarounds inDefaultExecuteContext
The text was updated successfully, but these errors were encountered: