Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 20 Sep 2016 07:33:20 +0000 (UTC)
From: "Alexey Kuznetsov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13006128.1474356750000.613478.1474356800512@Atlassian.JIRA>
In-Reply-To: <JIRA.13006128.1474356750000@Atlassian.JIRA>
References: <JIRA.13006128.1474356750000@Atlassian.JIRA> <JIRA.13006128.1474356750419@arcas>
Subject: [jira] [Created] (IGNITE-3938) JDBC POJO should support escaping
 for database schema, table and field names
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 20 Sep 2016 07:33:22 -0000

Alexey Kuznetsov created IGNITE-3938:
----------------------------------------

             Summary: JDBC POJO should support escaping for database schema, table and field names
                 Key: IGNITE-3938
                 URL: https://issues.apache.org/jira/browse/IGNITE-3938
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 1.6
            Reporter: Alexey Kuznetsov
            Assignee: Alexey Kuznetsov
             Fix For: 1.8


Sometimes database names could be very *strange* and this could be handled only via escaping. We need to support this.
Adding {code}String JdbcDialect.escape(name){code} method looks like a good solution.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)