You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some databases use extended schema name like "catalog"."schema" instead of simply "schema".
Currently on Flyway CLI, when flyway.schemas or flyway.defaultSchema configuration keys are set with catalog.schema value, CLI uses "catalog.schema" (instead of "catalog"."schema").
If I put "catalog"."schema" name in configuration, flyway CLI guess this erroneous schema: ""catalog"."schema""
Which version and edition of Flyway are you using?
10.17.1 Opensource edition.
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
CLI
Which database are you using? (Type & version)
Trino, but not releated to any specific database type.
Which operating system are you using?
Windows
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
see above
What did you expect to see?
see above
What did you see instead?
see above
The text was updated successfully, but these errors were encountered:
humpfhumpf
changed the title
CLI does not support "catalog"."schema" extended name for schema configuration
CLI does not support "catalog"."schema" qualified name for schema configuration
Nov 8, 2024
Hi @humpfhumpf ,
In this case, you need to include escape character. The below configuration in a toml file works: defaultSchema = "\"catalog\".\"schema\""
Some databases use extended schema name like "catalog"."schema" instead of simply "schema".
Currently on Flyway CLI, when
flyway.schemas
orflyway.defaultSchema
configuration keys are set with catalog.schema value, CLI uses "catalog.schema" (instead of "catalog"."schema").If I put "catalog"."schema" name in configuration, flyway CLI guess this erroneous schema: ""catalog"."schema""
One of the cause seems to be here: https://github.com/flyway/flyway/blob/main/flyway-core/src/main/java/org/flywaydb/core/internal/database/base/Schema.java#L221
Which version and edition of Flyway are you using?
10.17.1 Opensource edition.
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Main branch is also impacted: https://github.com/flyway/flyway/blob/main/flyway-core/src/main/java/org/flywaydb/core/internal/database/base/Schema.java#L221
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
CLI
Which database are you using? (Type & version)
Trino, but not releated to any specific database type.
Which operating system are you using?
Windows
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
see above
What did you expect to see?
see above
What did you see instead?
see above
The text was updated successfully, but these errors were encountered: