jdbi | provide convenient tabular data access in Java

Let's consider Jdbi 3.27.0.

Please, see the Javadoc for the org.jdbi.v3.core.Jdbi#inTransaction(org.jdbi.v3.core.HandleCallback) method:

inTransaction

public Exception> R inTransaction (HandleCallback callback) throws X

A convenience function which manages the lifecycle of a handle and yields it to a callback for use by clients. The handle will be in a transaction when the callback is invoked, and that transaction will be committed if the callback finishes normally, or rolled back if the callback raises an exception.

Type Parameters:

R - type returned by the callback

X - exception type thrown by the callback, if any.

Parameters:

callback - A callback which will receive an open Handle, in a transaction

Returns:

the value returned by callback

Throws:

X - any exception thrown by the callback

Please, note the text marked in bold, which should answer your question:

The handle will be in a transaction when the callback is invoked, and that transaction will be committed if the callback finishes normally, or rolled back if the callback raises an exception.

Throws:

X - any exception thrown by the callback

As we can see, there is no statement claiming that the exception handling behavior depends on the exception type.

Please, consider the information provided in this section as a draft: it may be rough (imprecise).

There are tests that cover the transaction-related functionality.
The tests are represented by the TestTransactions class: jdbi/TestTransactions.java at v3.27.0 · jdbi/jdbi.

Please, take a look at the entire test class.

Then, please, note the following exception-related test methods:

1. testExceptionAbortsTransaction().
2. testExceptionAbortsUseTransaction().

As we can examine from the implementations of these test methods:

1. The implementations use the java.io.IOException exception type.
2. The implementations does not mention that the exception handling behavior depends on the exception type.

For in clause you should use bindList with syntax, example from the JDBI doc

JDBI documentation clearly states:

Use ConstructorMapper or @RegisterConstructorMapper to map @Value classes.

So your code might look like this (but probably there is no need to register row mapper on each call, it could be done on global level):

Will there be a new connection / transaction for each insert called or will they all be grouped into one transaction?

Calls to dao2 will be grouped in one transaction from explicitly opened handle.

Calls to dao1 will use separate transaction per each method call (from Jdbi#onDemand javadoc: an extension which opens and closes handles (as needed) for individual method calls).

If you want to execute methods from different SqlObject's in the scope of transaction, you have several options:

• Jdbi#inTransaction/Jdbi#useTransaction: works for both onDemand/attach
• Combination of @Transaction and @CreateSqlObject, as in the docs

You need to escape < (change to \\<) symbol in your query since it is the same as used by template engine.

EDIT: Adding to the answer for more specificity, the issue is at

" < NOW() - INTERVAL ''"

which needs to be

" \\< NOW() - INTERVAL ''"

Add the following to build.gradle. After rebuilding the project, see if the error goes away.

yes , it works with AgroalDataSource

Types cannot be inferred, because your functional interface JdbiCall doesn't have neither generics at the class declaration level nor parameters for call method by which these types can be inferred. So, your FI might look like this:

The point of that X extends Exception is for your code, not JDBI's code. The code you write yourself (after the ->) can throw X.

JDBI will indeed be throwing JdbiExceptions, and won't be throwing anything else. But YOUR CODE might e.g. throw IOException or whatnot.

This works: