[ https://issues.apache.org/jira/browse/IGNITE-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067598#comment-15067598 ]
Denis Magda commented on IGNITE-1979: ------------------------------------- Guys, We need to be sure that there is no performance drop as well for a standard use case - without a schema being set. Also I would run benchmarks for the case with a schema being set explicitly. > 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: Pavel Konstantinov > 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)