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
{{ message }}
Repository navigation
Manual SQL generated doesn't honor db schema
#15658
I've recently worked on two Keycloak upgrades, from 12.x to 19.0.1 (Quarkus) and from 19.0.1 to 20.0.1. Our Keycloak is configured, using spi-connections-jpa-legacy-migration-strategy=manual, to generate manual SQL that we then run. Our Keycloak is also configured to use a database schema. In upgrading to 19.0.1, some of the SQL honored the schema, some did not. In upgrading from 19.0.1 to 20.0.1, none of the SQL honored the schema. Is it expected that this manual SQL should include the correct schema if one is specified in configuration? Or is there some alternate configuration I'm missing? Just trying to determine if this is a bug. Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I've recently worked on two Keycloak upgrades, from 12.x to 19.0.1 (Quarkus) and from 19.0.1 to 20.0.1. Our Keycloak is configured, using
spi-connections-jpa-legacy-migration-strategy=manual, to generate manual SQL that we then run. Our Keycloak is also configured to use a database schema. In upgrading to 19.0.1, some of the SQL honored the schema, some did not. In upgrading from 19.0.1 to 20.0.1, none of the SQL honored the schema. Is it expected that this manual SQL should include the correct schema if one is specified in configuration? Or is there some alternate configuration I'm missing? Just trying to determine if this is a bug. Thanks!All reactions