Upgrade to Keycloak 25 - Table 'USER_CONSENT' is specified twice on MySQL/MariaDB database #30304
Conversation
Signed-off-by: Nicola Beghin <[email protected]>
stianst
left a comment
There was a problem hiding this comment.
As this will be included in 26, and probably backported to 25.0.1, what happens in the case someone has already upgraded to 25.0.0?
I'm not sure, but the hash is based on the id and it won't run again. @sguilhen Makes sense? |
|
I'm not 100% sure how the checksum is calculated in Liquibase - it is definitely not based on the id. I believe it is calculated based on the SQL output of the changeset. @stianst I've tested this scenario. Started Keycloak 25 using a supported version of MariaDB, changeset was executed without errors. Then migrated to a 999-SNAPSHOT version including this change. The migration ran fine, it didn't complain about checksums. So I don't think it will a problem for those who already migrated to 25. The question is, should we do it given that users on supported versions of MariaDB don't run into any issues and the upgrade to 25 is problematic only for people running unsupported versions of the DB? |
Closes #30300
ref. @cgeorgilakis @ahus1 from original commit 4bca804
Upgrade to Keycloak 25 - Table 'USER_CONSENT' is specified twice on MySQL/MariaDB database