[
https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021838#comment-15021838
]
Sergi Vladykin commented on IGNITE-1979:
----------------------------------------
Denis, actually you are wrong about ANSI SQL standard. Double quoted
identifiers is a standard SQL feature since SQL ANSI-92.
It is defined as
{code}
<delimited identifier> ::=
<double quote> <delimited identifier body> <double quote>
{code}
And purpose of it is to handle cases when we need case sensitive names or names
with special characters.
The spec itself is a bit cryptic, but Oracle documentation states it clear:
https://docs.oracle.com/database/121/SQLRF/sql_elements008.htm#SQLRF51129
{code}
Nonquoted identifiers are not case sensitive. Oracle interprets them as
uppercase. Quoted identifiers are case sensitive.
{code}
> Cache name requirement violates SQL ANSI-99 standard
> ----------------------------------------------------
>
> 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
> 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 to turn off current Ignite requirement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
