Regression: "INTERNAL Error: Attempting to commit a transaction that is read-only but has made changes" when generating sequence values from generate_series table with bind value arguments

[lukaseder]

Create a sequence like this:

create sequence s;

Then try to generate sequence values like this:

try (PreparedStatement s = connection.prepareStatement("select nextval('s') from generate_series(?, ?)")) {
    s.setInt(1, 1);
    s.setInt(2, 5);

    try (ResultSet rs = s.executeQuery()) {
        while (rs.next()) {
            System.out.println(rs.getInt(1));
        }
    }
}

This produces the following error:

0
INTERNAL Error: Attempting to commit a transaction that is read-only but has made changes - this should not be possible
This error signals an assertion failure within DuckDB. This usually occurs due to unexpected conditions or errors in the program's logic.
For more information, see https://duckdb.org/docs/dev/internal_errors
null
java.sql.SQLException: INTERNAL Error: Attempting to commit a transaction that is read-only but has made changes - this should not be possible
This error signals an assertion failure within DuckDB. This usually occurs due to unexpected conditions or errors in the program's logic.
For more information, see https://duckdb.org/docs/dev/internal_errors
	at org.duckdb.DuckDBNative.duckdb_jdbc_execute(Native Method)
	at org.duckdb.DuckDBPreparedStatement.execute(DuckDBPreparedStatement.java:143)
	at org.duckdb.DuckDBPreparedStatement.executeQuery(DuckDBPreparedStatement.java:175)
	at org.jooq.testscripts.JDBC.main(JDBC.java:42)

This is a regression introduced in 0.10.3, still present in 1.0.0. It used to work in 0.10.2.

A workaround is to avoid bind values in generate_series(), like this:

try (PreparedStatement s = connection.prepareStatement("select nextval('s') from generate_series(1, 5)")) {
    try (ResultSet rs = s.executeQuery()) {
        while (rs.next()) {
            System.out.println(rs.getInt(1));
        }
    }
}

This now prints:

2
3
4
5
6