Writing method which are using ReturningMode.NONE return the number of affected rows instead.

What a write answers with when it returns no rows. On, it is the number of rows the statement changed; off, the method is void.

The count is worth having: an update that changed no rows is usually a bug the caller can act on, and there is nowhere else to learn that. Turn it off for a statement whose count is meaningless — a create table, or DDL generally.

This applies to returning none only. A write that returns rows answers with them.

Configuration Options

Option: ’true'

The default. The caller can see how many rows the statement changed:

public final class TenantRepository {

    public int insertTenant(final UUID id, final String slug) {
        // ... rest of generated code
    }

}

Option: ‘false’

The count is dropped:

public final class TenantRepository {

    public void insertTenant(final UUID id, final String slug) {
        // ... rest of generated code
    }

}

Related Options

Also in this group: annotations , catchAndRethrow , createConnection , description , executeBatch , executeOnce , generateConnectionOverloads , generateResultRowType , injectConverter , name , parameters , repository , resultRowColumns , resultRowConverter , resultRowType , returningMode , throwOnMultipleResults , type , validateSchema , vendor .

Front Matter

In order to configure this option, place the following code in the front matter of your SQL statement:

-- writesReturnUpdateCount: true
SELECT  something
FROM    your_database_schema
WHERE   some_column = :some_value