@Anchels thank you for the PR, are you able to add a test for this case as well?

@shawkins sorry, I don't have experience with writing tests

@shawkins sorry, I don't have experience with writing tests

No problem.

@rmartinc @sguilhen @ahus1 can you review and indicate whether you want a test case?

Not sure if this fix is enough - see https://github.com/keycloak/keycloak/blob/main/model/jpa/src/main/java/org/keycloak/connections/jpa/updater/liquibase/lock/CustomLockService.java#L130-L139

The CustomInitializeDatabaseChangeLogLockTableStatement in line 139 should probably be using the ids from the Namespace enum. As it stands now, it is updating the table with the same values it has read in line 130. So, to me, besides fixing the wrong type comparison we should also fix the initialization to set the ids from the enum

@sguilhen, could you please see if the latest changes will help fix the problem? Or should we combine currentIds with enum IDs for the initializatoin?

To be on the safe side I would combine them.