Error creating a true read only connection

[Borbarad13]

Describe the bug
It seems to be impossible to create a (truely) read only connection (open_mode = 1) or I might be missing something. I receive the error "SQLiteException: [SQLITE_MISUSE]", which could indicate that those connections are not wanted or that I use the library incorrectly to create them.

To Reproduce

   SQLiteConfig config = new SQLiteConfig();
        config.setOpenMode(SQLiteOpenMode.READONLY);
        try (Connection connection = DriverManager.getConnection(
                "jdbc:sqlite:sqlite", config.toProperties())) {
            } catch (SQLException e) {
            throw new RuntimeException(e);
        }

Expected behavior
Truely read only connections are possible to create (I am not talking about the mutable ones which switch around e.g. via "pragma query_only or via setReadOnly() ).

Logs

Exception in thread "main" java.lang.RuntimeException: org.sqlite.SQLiteException: [SQLITE_MISUSE] Library used incorrectly (bad parameter or other API misuse)
Caused by: org.sqlite.SQLiteException: [SQLITE_MISUSE] Library used incorrectly (bad parameter or other API misuse)
at org.sqlite.core.DB.newSQLException(DB.java:1179)
at org.sqlite.core.DB.newSQLException(DB.java:1190)
at org.sqlite.core.DB.throwex(DB.java:1150)
at org.sqlite.core.NativeDB._open_utf8(Native Method)
at org.sqlite.core.NativeDB._open(NativeDB.java:82)
at org.sqlite.core.DB.open(DB.java:216)
at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:268)
at org.sqlite.SQLiteConnection.(SQLiteConnection.java:67)

Environment (please complete the following information):

• OS: Ubuntu, AMD

Additional context
Add any other context about the problem here.

[gotson]

Check

sqlite-jdbc/src/test/java/org/sqlite/ConnectionTest.java

Lines 53 to 81 in 470c78c

	@Test
	public void readOnly() throws SQLException {
	// set read only mode
	SQLiteConfig config = new SQLiteConfig();
	config.setReadOnly(true);
	try (Connection conn = DriverManager.getConnection("jdbc:sqlite:", config.toProperties())) {
	try (Statement stat = conn.createStatement()) {
	assertThat(conn.isReadOnly()).isTrue();
	// these updates must be forbidden in read-only mode
	assertThatThrownBy(
	() -> {
	stat.executeUpdate("create table A(id, name)");
	stat.executeUpdate("insert into A values(1, 'leo')");
	})
	.isInstanceOf(SQLException.class);
	}
	conn.close();
	config.setReadOnly(true); // should be a no-op
	assertThatThrownBy(() -> conn.setReadOnly(false))
	.isInstanceOf(SQLException.class)
	.hasMessageContaining(
	"Cannot change read-only flag after establishing a connection.");
	}
	}

[Borbarad13]

This way of using the config works. I guess no bug then. Thanks gotson for pointing me in the right direction!