[
https://issues.apache.org/jira/browse/CALCITE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971681#comment-14971681
]
Josh Elser commented on CALCITE-521:
------------------------------------
We have some of these, but I'm not sure we have all.
Minimally, I highly doubt we have unit-test coverage for all of these requests
which I would say is required before saying we have them all implemented.
> Implement metadata requests in remote JDBC driver
> -------------------------------------------------
>
> Key: CALCITE-521
> URL: https://issues.apache.org/jira/browse/CALCITE-521
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> The remote JDBC driver supports getCatalogs() and getSchemas(), via requests
> CatalogsRequest and SchemasRequest. We need to implement more methods:
> * getTables
> * getColumns
> * getTableTypes
> * getProcedures
> * getProcedureColumns
> * getColumnPrivileges
> * getTablePrivileges
> * getBestRowIdentifier
> * getVersionColumns
> * getPrimaryKeys
> * getImportedKeys
> * getExportedKeys
> * getCrossReference
> * getTypeInfo
> * getIndexInfo
> * getUDTs
> * getSuperTypes
> * getSuperTables
> * getAttributes
> * getClientInfoProperties
> * getFunctions
> * getFunctionColumns
> * getPseudoColumns
> Many of these will return empty sets when run against Calcite, because
> Calcite doesn't override the MetaImpl, and the default implementation returns
> empty. That's OK. This task is just to create the plumbing from client to
> server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
