- All Implemented Interfaces:
This implementation wraps a JDBC
DataSource. jOOQ will use that data
source for initialising connections, and creating statements.
Use this connection provider if you want to run distributed transactions,
javax.transaction.UserTransaction. jOOQ will
close() all connections after query execution (and
result fetching) in order to return the connection to the connection pool. If
you do not use distributed transactions, this will produce driver-specific
behaviour at the end of query execution at
(e.g. a transaction rollback). Use a
instead, to control the connection's lifecycle, or implement your own
- Aaron Digulla, Lukas Eder
DataSourceConnectionProviderpublic DataSourceConnectionProvider(DataSource dataSource)
dataSource@NotNull public @NotNull DataSource dataSource()
acquire@NotNull public @NotNull Connection acquire()Description copied from interface:
ConnectionProviderAcquire a connection from the connection lifecycle handler.
This method is called by jOOQ exactly once per execution lifecycle, i.e. per
ExecuteContext. Implementations may freely chose, whether subsequent calls to this method:
- return the same connection instance
- return the same connection instance for the same thread
- return the same connection instance for the same transaction (e.g. a
- return a fresh connection instance every time
jOOQ will guarantee that every acquired connection is released through
releasepublic void release(Connection connection)Description copied from interface:
ConnectionProviderRelease a connection to the connection lifecycle handler.
jOOQ will guarantee that every acquired connection is released exactly once.