calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Hyde (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CALCITE-3048) Improve how JDBC adapter deduces current schema on Redshift
Date Fri, 03 May 2019 06:55:00 GMT
Julian Hyde created CALCITE-3048:
------------------------------------

             Summary: Improve how JDBC adapter deduces current schema on Redshift
                 Key: CALCITE-3048
                 URL: https://issues.apache.org/jira/browse/CALCITE-3048
             Project: Calcite
          Issue Type: Bug
            Reporter: Julian Hyde


Improve how JDBC adapter deduces current schema on Amazon Redshift or PostgreSQL. Until now,
we either look at the schema connect-string parameter, or call {{Connection.getSchema()}}
(on JDBC 4.1 and above). But in Redshift's JDBC driver, {{Connection.getSchema()}} always
returns null.

Now, if we know we are running against Redshift or PostgreSQL, we will execute a {{select
current_schema()}} query to find the current schema.

Similarly for {{Connection.getCatalog()}} and {{select current_database()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message