ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6125) Improve robustness for JDBC driver metadata queries
Date Tue, 22 Aug 2017 07:48:00 GMT

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

Ilya Kasnacheev updated IGNITE-6125:
------------------------------------
    Description: 
org.apache.ignite.internal.jdbc2.JdbcDatabaseMetadata is in worrysome state:

- Makes frivolous use of toUpperCase() to address former.
- getPrimaryKeys() never returns anything because of defective use of toUpperCase().
- No tests on indexes, primary keys, schemas or parameters metadata retrieval.
- Ignores "catalog" parameter instead of checking if it matches empty catalog.
- See also IGNITE-6138, IGNITE-6139

That should be fixes without compromising backwards compatibility too much. Tests may be borrowed
from thin client implementation.

  was:
org.apache.ignite.internal.jdbc2.JdbcDatabaseMetadata is in worrysome state:

- Uses cache name instead of schema and type name instead of table.
- Makes frivolous use of toUpperCase() to address former.
- getPrimaryKeys() never returns anything because of defective use of toUpperCase().
- No tests on indexes, primary keys, schemas or parameters metadata retrieval.
- get*Version returns hardcoded obsolete values.
- Ignores "catalog" parameter instead of checking if it matches empty catalog.

That should be fixes without compromising backwards compatibility too much. Tests may be borrowed
from thin client implementation.

        Summary: Improve robustness for JDBC driver metadata queries  (was: A range of improvements
for JDBC driver metadata queries)

> Improve robustness for JDBC driver metadata queries
> ---------------------------------------------------
>
>                 Key: IGNITE-6125
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6125
>             Project: Ignite
>          Issue Type: Improvement
>          Components: clients, jdbc
>    Affects Versions: 2.1
>            Reporter: Ilya Kasnacheev
>            Assignee: Ilya Kasnacheev
>
> org.apache.ignite.internal.jdbc2.JdbcDatabaseMetadata is in worrysome state:
> - Makes frivolous use of toUpperCase() to address former.
> - getPrimaryKeys() never returns anything because of defective use of toUpperCase().
> - No tests on indexes, primary keys, schemas or parameters metadata retrieval.
> - Ignores "catalog" parameter instead of checking if it matches empty catalog.
> - See also IGNITE-6138, IGNITE-6139
> That should be fixes without compromising backwards compatibility too much. Tests may
be borrowed from thin client implementation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message