[jira] [Assigned] (IGNITE-3467) jdbc getTables() returns catalog as null
[ https://issues.apache.org/jira/browse/IGNITE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kuznetsov reassigned IGNITE-3467: --- Assignee: Pavel Kuznetsov > jdbc getTables() returns catalog as null > > > Key: IGNITE-3467 > URL: https://issues.apache.org/jira/browse/IGNITE-3467 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 1.6 >Reporter: Alexandre Boudnik >Assignee: Pavel Kuznetsov >Priority: Major > Labels: usability > > Then some jdbc query tool uses null values as catalog name. An H2 database > returns word "DATABASE" in CATALOG column, and then correctly resolves a > fully-qualified name. I would recommend to do the same for these metadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-3467) jdbc getTables() returns catalog as null
[ https://issues.apache.org/jira/browse/IGNITE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-3467: --- Assignee: (was: Alexandre Boudnik) > jdbc getTables() returns catalog as null > > > Key: IGNITE-3467 > URL: https://issues.apache.org/jira/browse/IGNITE-3467 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 1.6 >Reporter: Alexandre Boudnik >Priority: Critical > > Then some jdbc query tool uses null values as catalog name. An H2 database > returns word "DATABASE" in CATALOG column, and then correctly resolves a > fully-qualified name. I would recommend to do the same for these metadata. -- This message was sent by Atlassian JIRA (v6.4.14#64029)