[
https://issues.apache.org/jira/browse/IGNITE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050980#comment-15050980
]
Nikolay Tikhonov commented on IGNITE-1993:
------------------------------------------
Hi Nigel,
Thank for your contribution!
I've tested your changes on Oracle and found that when table doesn't exist this
code doesn't work correct yet.
I think that the right way to allow users use own sql query for working with
data base (create/insert/delete/select operations).
Thoughts?
> 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)
