Skip to content

Resolve db-schema case via Hibernate in DatabaseIndexChecker - #55220

Draft
ahus1 wants to merge 1 commit into
keycloak:mainfrom
ahus1:is-54836-index-checker-schema-case
Draft

ahus1 wants to merge 1 commit into
keycloak:mainfrom
ahus1:is-54836-index-checker-schema-case

Conversation

@ahus1

@ahus1 ahus1 commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Closes #54836

Decisions and assumptions:

  • The configured schema is resolved with Hibernate's IdentifierHelper instead of folding case in the checker, so the checker looks at the same schema Hibernate uses for the unquoted name.
  • Verified on PostgreSQL with CaseSensitiveSchemaTest, PreserveSchemaCaseLiquibaseTest and a temporary mixed-case dash schema test (Keycloak-T); no "Failed to create index" warnings remain.
  • No new test, as CaseSensitiveSchemaTest already reproduces the issue.

Closes keycloak#54836

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Alexander Schwartz <alexander.schwartz@ibm.com>
@ahus1
ahus1 force-pushed the is-54836-index-checker-schema-case branch from 6dae682 to 837c7ce Compare November 16, 2026 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DatabaseIndexChecker logs a warning for every index when db-schema case differs from the actual schema

1 participant