[
https://issues.apache.org/jira/browse/IGNITE-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191442#comment-16191442
]
Taras Ledkov edited comment on IGNITE-6556 at 10/4/17 3:35 PM:
---------------------------------------------------------------
What about the caches without specified sql schema. When {{cacheName}} is used
to create SQL schema? In this case *cacheName* isn't modified.
e.g.:
{code}
cacheConfiguration.setName("person");
...
conn.setSqlSchema("person");
{code} fail with error "Failed to set schema for DB connection for thread
[schema="PERSON"]"
Is it OK or incompatible behavior?
was (Author: tledkov-gridgain):
What about the caches without specified sql schema. When {{cacheName}} is used
to create SQL schema? In this case *cacheName* isn't modified.
e.g.:
code}
cacheConfiguration.setName("person");
...
conn.setSqlSchema("person");
{code} fail with error "Failed to set schema for DB connection for thread
[schema="PERSON"]"
Is it OK or incompatible behavior?
> setSchema() is case sensitive in the wrong way in Thin JDBC driver
> ------------------------------------------------------------------
>
> Key: IGNITE-6556
> URL: https://issues.apache.org/jira/browse/IGNITE-6556
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.2
> Reporter: Ilya Kasnacheev
> Assignee: Taras Ledkov
> Fix For: 2.3
>
>
> Suppose we have a cache with
> {code}
> cacheCfg.setSqlSchema("emp");
> {code}
> Then, both
> {code}
> conn.setSchema("emp");
> conn.setSqlSchema("\"emp\"");
> {code} fail with error "Failed to set schema for DB connection for thread
> [schema="emp"]"
> And only
> {code}
> conn.setSchema("EMP");
> {code}
> works which is confusing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
