Skip to content

Fix metadata identifiers containing backticks#1473

Closed
msrathore-db wants to merge 1 commit into
databricks:mainfrom
msrathore-db:fix-metadata-backtick-identifiers
Closed

Fix metadata identifiers containing backticks#1473
msrathore-db wants to merge 1 commit into
databricks:mainfrom
msrathore-db:fix-metadata-backtick-identifiers

Conversation

@msrathore-db
Copy link
Copy Markdown
Collaborator

Summary

  • Escape literal backticks before interpolating catalog, schema, and table identifiers into metadata SQL commands.
  • Apply the same escaping to information_schema catalog prefixes used by procedure metadata.
  • Add regression coverage for primary keys, foreign keys, other metadata commands, and information_schema catalog prefixes.

Test plan

  • mvn test -pl jdbc-core -Dtest=CommandBuilderTest,CommandConstantsTest

Fixes #1471

Escape literal backticks before interpolating JDBC metadata identifiers into backtick-delimited Databricks SQL commands.

Signed-off-by: Madhavendra Rathore <madhavendra.rathore@databricks.com>
@msrathore-db
Copy link
Copy Markdown
Collaborator Author

Superseded by #1474, which uses a branch pushed directly to databricks/databricks-jdbc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] getPrimaryKeys fails when catalog, schema or table name contains backtick

1 participant