Construct a new Transactor
that uses the JDBC DriverManager
to allocate connections.
Construct a new Transactor
that uses the JDBC DriverManager
to allocate connections.
the class name of the JDBC driver, like "org.h2.Driver"
a connection URL, specific to your driver
a Properties
containing connection information (see DriverManager.getConnection
)
Construct a new Transactor
that uses the JDBC DriverManager
to allocate connections.
Construct a new Transactor
that uses the JDBC DriverManager
to allocate connections.
the class name of the JDBC driver, like "org.h2.Driver"
a connection URL, specific to your driver
database username
database password
Construct a new Transactor
that uses the JDBC DriverManager
to allocate connections.
Construct a new Transactor
that uses the JDBC DriverManager
to allocate connections.
the class name of the JDBC driver, like "org.h2.Driver"
a connection URL, specific to your driver
Module of constructors for
Transactor
that use the JDBCDriverManager
to allocate connections. Note thatDriverManager
is unbounded and will happily allocate new connections until server resources are exhausted. It is usually preferable to useDataSourceTransactor
with an underlying bounded connection pool (as withH2Transactor
andHikariTransactor
for instance). Blocking operations onDriverManagerTransactor
are executed on an unbounded cached daemon thread pool, so you are also at risk of exhausting system threads. TL;DR this is fine for console apps but don't use it for a web application.