Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MetaData patterns in schema for getPrimaryKeys, getExportedKeys and getImportedKeys #1217

Closed
ovna01 opened this issue Jan 2, 2023 · 1 comment
Assignees
Labels
Backlog feature status-triage_done Initial triage done, will be further handled by the driver team

Comments

@ovna01
Copy link

ovna01 commented Jan 2, 2023

Hi,

I am a developer in the team that works with the DbVisualizer tool.
We noticed that the metadata calls for getPrimaryKey, getExportedKeys and getImportedKeys allows patterns for schema (from version 3.13.19?).
According to the JDBC documentation patterns is not valid for schema in those calls, see getPrimaryKeys

As these MetaData calls is used by our tool, we have added a WO to escape the schema for above calls in Snowflake.
However, we need to know if the addition of patterns for schema is intentional or an error.
Please, inform us if you should remove the support for patterns in the schema, so that we can remove the WO.
[email protected]

@sfc-gh-dszmolka sfc-gh-dszmolka added the status-triage_done Initial triage done, will be further handled by the driver team label Apr 26, 2024
@sfc-gh-dszmolka
Copy link
Contributor

this should now be resolved with #1639 which is released in 3.15.0 and added a new connection parameter enablePatternSearch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog feature status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

4 participants