[
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055618#comment-15055618
]
Denis Magda commented on IGNITE-1979:
-------------------------------------
Vladimir, please make sure that if a user specified
CacheConfiguration.setSqlSchema(String schema) directly then a cache name
(schema name) in the query must be case insensitive. Otherwise we will violate
the standard.
As a example, if we set CacheConfiguration.setSqlSchema to "my_cache" then in
queries I will be able to use schema names like:
- select * from "My_cache"....
- select * from "my_CAche"...
- etc.
In addition please make sure to add new tests to check this functionality and
the cases described by me above.
> Support case insensitive nonquoted cache names in SQL queries
> -------------------------------------------------------------
>
> Key: IGNITE-1979
> URL: https://issues.apache.org/jira/browse/IGNITE-1979
> Project: Ignite
> Issue Type: Bug
> Components: SQL
> Affects Versions: ignite-1.4
> Reporter: Denis Magda
> Assignee: Vladimir Ershov
> Priority: Critical
> Fix For: 1.5
>
>
> According to SQL ANSI-99 standard the schema name (corresponds to a cache
> name in Ignite) is case insensitive.
> However Ignite has the requirement to put a cache name into the quotation
> marks. This violates the standard.
> The main reasons of that is because a cache name in Ignite is case sensitive
> and can contain all kind of symbols that are not supported by underlying H2
> engine.
> Proposed to introduce a new configuration property to {{CacheConfiguration}}
> that will let the end user use a cache name in case insensitive manner
> without quoted identifiers in SQL queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
