You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/10/01 21:54:26 UTC
[jira] [Commented] (CALCITE-905) getTables returns empty result in
JdbcMeta
[ https://issues.apache.org/jira/browse/CALCITE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940305#comment-14940305 ]
Julian Hyde commented on CALCITE-905:
-------------------------------------
Patch looks good, but can you also supply a unit test.
> getTables returns empty result in JdbcMeta
> ------------------------------------------
>
> Key: CALCITE-905
> URL: https://issues.apache.org/jira/browse/CALCITE-905
> Project: Calcite
> Issue Type: Bug
> Reporter: Jan Van Besien
> Assignee: Julian Hyde
> Attachments: CALCITE-905.patch
>
>
> getTables on the metadata of a connection does not work (returns empty ResultSet) with avatica remoting using a JdbcMeta.
> {code}
> connection.getMetaData().getTables(null, null, null, null);
> {code}
> The problem seems to be related to the String[] types argument of the getTables method, this works as expected:
> {code}
> connection.getMetaData().getTables(null, null, null, new String[]{"TABLE"});
> {code}
> I think it boils down to the JdbcMeta#toArray(List<String> typeList) method which returns an empty array in stead of null, resulting in the creation of an incorrect typeFilter in CalciteMetaImpl#getTables (line 254).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)