You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/10/21 20:08:28 UTC

[jira] [Updated] (CALCITE-522) In remote JDBC driver, transmit static database properties as a map

     [ https://issues.apache.org/jira/browse/CALCITE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated CALCITE-522:
-------------------------------
    Component/s: avatica

> In remote JDBC driver, transmit static database properties as a map
> -------------------------------------------------------------------
>
>                 Key: CALCITE-522
>                 URL: https://issues.apache.org/jira/browse/CALCITE-522
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 1.3.0-incubating
>
>
> A lot of DatabaseMetaData methods are not parameterized, and give the same answer every time. Some examples:
> * allProceduresAreCallable
> * getUserName
> * isReadOnly
> * getDatabaseProductName
> * getDatabaseProductVersion
> * getDriverName
> * getDriverVersion
> * getDriverMajorVersion
> * getDriverMinorVersion
> * getSqlKeywords
> * getNumericFunctions
> * getStringFunctions
> * getSystemFunctions
> * getTimeDateFunctions
> This task would define an enum of properties, add a method to Meta that returns (property, value) map.
> See DatabaseMetaData and Connection for the full list.
> Obsolete the following Meta methods:
> * getSqlKeywords
> * getNumericFunctions
> * getStringFunctions
> * getSystemFunctions
> * getTimeDateFunctions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)