You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2015/12/01 08:59:11 UTC

[jira] [Commented] (IGNITE-1993) JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)

    [ https://issues.apache.org/jira/browse/IGNITE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033288#comment-15033288 ] 

Denis Magda commented on IGNITE-1993:
-------------------------------------

Nigel,

Do you need any assistance on running the tests?

> 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
>              Labels: easyfix, patch
>             Fix For: 1.4
>
>         Attachments: IGNITE1993.patch
>
>
> 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)