You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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]
The text was updated successfully, but these errors were encountered:
Hi,
I am a developer in the team that works with the DbVisualizer tool.
We noticed that the metadata calls for
getPrimaryKey
,getExportedKeys
andgetImportedKeys
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]
The text was updated successfully, but these errors were encountered: