No way to disable JDBC offset table creation

The documentation for RDBMS read-side support says:

Lagom will store the offsets in a table that it will automatically create itself if it doesn’t exist. If you would prefer that Lagom didn’t automatically create this table for you, you can turn off this feature by setting lagom.persistence.jdbc.create-tables.auto=false in application.conf.

Lagom does not currently check this setting when creating the offsets table; it is created unconditionally (if it doesn’t already exist).

[TimMoore]

Thanks, @jousby. By the way, this issue was fixed in 1.3.0-RC2 (released a couple of days ago), so you should be able to disable creation if you update.

[jousby]

@TimMoore So I believe was hitting the issue you highlighted above at some point:

@jousby OK I’ve got it now… it’s actually the MySQL emulation causing the issue. Specifically, “Meta data calls return identifiers in lower case” (from H2 > Features > Compatibility). This means it’s returning “public” as the schema name, when the schema is actually stored as “PUBLIC”.

Lagom is comparing both the schema name and the table name when searching for an existing table, and the query it is using to detect the current schema returns it as stored, in uppercase, while the metadata query it is using to get the list of tables returns it in lowercase when running in this mode.

I’ll see if there’s a way we can query for the current schema in a different way that takes this mode into account.

However there is a second issue I was also bumping into while trying to use schema’s other than PUBLIC. I’ve created an issue for this here https://github.com/lagom/lagom/issues/498.