[jira] [Commented] (IGNITE-14214) Incorrect merge query when using oracle dialect

["Alexey Gidaspov (Jira)" <ji...@apache.org>]

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

Alexey Gidaspov commented on IGNITE-14214:
------------------------------------------

Hello [~NSAmelchev],
I see 'Release Notes Required' flag is set and no release note attached. Please add release note or remove the flag. Thank you. 
 

> Incorrect merge query when using oracle dialect
> -----------------------------------------------
>
>                 Key: IGNITE-14214
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14214
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.10, 2.9.1
>            Reporter: Yaroslav Molochkov
>            Assignee: Amelchev Nikita
>            Priority: Major
>             Fix For: 2.11
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> If table contains only keys (e.g. relationship table) then returned query contains empty update fields and resulting syntax is incorrect. 
> Consider the following example:
> org.apache.ignite.cache.store.jdbc.dialect.OracleDialect#mergeQuery accepts key and val collections. The problem is relevant if val collection is empty.
> {code:java}
> return String.format("MERGE INTO %s t" +
>     " USING (SELECT %s FROM dual) v" +
>     "  ON %s" +
>     " WHEN MATCHED THEN" +
>     "  UPDATE SET %s" +
>     " WHEN NOT MATCHED THEN" +
>     "  INSERT (%s) VALUES (%s)", fullTblName, selCols, match, setCols, colsLst, valuesCols);
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)