[
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062205#comment-15062205
]
Sergi Vladykin commented on IGNITE-1979:
----------------------------------------
Denis, again it is a wrong test and your appeal to the standard is wrong as
well.
Please avoid such claims until you really know what you are talking about, you
are confusing
other developers and users looking after this issue.
The correct behavior is:
{code}
// If the property is set to
ccfg.setSqlSchema("my_cache");
// Then it must be possible to run queries like the following:
SELECT * FROM MY_CACHE.PERSON
SELECT * FROM mY_Cache.Person
// etc...
// If the property is set to
ccfg.setSqlSchema("\"my_cache\"");
// Then it will be only possible to run queries like
SELECT * FROM "my_cache".PERSON
{code}
If CacheConfiguration.setSqlEscapeAll set to true then we have to add quotes to
sqlSchema property (if there are none).
> 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.6
>
>
> 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)
