Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 24 Nov 2015 15:35:11 +0000 (UTC)
From: "Nigel Westbury (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.12915822.1448379274000.176980.1448379311244@Atlassian.JIRA>
In-Reply-To: <JIRA.12915822.1448379274000@Atlassian.JIRA>
References: <JIRA.12915822.1448379274000@Atlassian.JIRA>
 <JIRA.12915822.1448379274674@arcas>
Subject: [jira] [Created] (IGNITE-1993) JDBC discovery uses non-standard SQL
 when creating table (not compatible with Oracle)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Nigel Westbury created IGNITE-1993:
--------------------------------------

             Summary: JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)
                 Key: IGNITE-1993
                 URL: https://issues.apache.org/jira/browse/IGNITE-1993
             Project: Ignite
          Issue Type: Bug
          Components: SQL
    Affects Versions: ignite-1.4
         Environment: Oracle database
            Reporter: Nigel Westbury


The SQL used by TcpDiscoveryJdbcIpFinder to create the table (defined by CREATE_ADDRS_TABLE_QRY) uses 'if not exists' clause.  However this clause is not supported by Oracle and causes SQLSyntaxErrorException: "ORA-00922: missing or invalid option" to be thrown.  This prevents JDBC discovery from being used with an Oracle database.


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