Support parsing Oracle MERGE USING sql
Background
Hi community, This issue is for #26878.
ShardingSphere parser engine helps users parse a SQL to get the AST (Abstract Syntax Tree) and visit this tree to get SQLStatement (Java Object). Currently, we are planning to enhance the support for Oracle SQL parsing in ShardingSphere.
More details: https://shardingsphere.apache.org/document/current/en/reference/sharding/parse/
Task
This issue is to support more oracle sql parse, as follows:
MERGE
USING Product_Changes S -- Source/Delta table
INTO Products P -- Destination table 1
ON (P.PROD_ID = S.PROD_ID) -- Search/Join condition
WHEN MATCHED THEN
UPDATE -- update if join
SET P.PROD_LIST_PRICE = S.PROD_NEW_PRICE
WHERE P.PROD_STATUS <> "OBSOLETE" -- Conditional UPDATE
MERGE USING New_Product S -- Source/Delta table
INTO Products D2 -- Destination table 2
ON (D2.PROD_ID = S.PROD_ID) -- Search/Join condition
WHEN NOT MATCHED THEN -- insert if no join
INSERT (PROD_ID, PROD_STATUS) VALUES (S.PROD_ID, S.PROD_NEW_STATUS)
MERGE USING New_Product S -- Source/Delta table
INTO Products P -- Destination table 1
ON (1 = 0) -- Search/Join condition
WHEN NOT MATCHED THEN -- insert if no join
INSERT (PROD_ID, PROD_STATUS) VALUES (S.PROD_ID, S.PROD_NEW_STATUS)
MERGE USING Product_Changes S
INTO Products D ON (D.PROD_ID = S.PROD_ID)
WHEN MATCHED THEN
UPDATE SET D.PROD_LIST_PRICE =S.PROD_NEW_PRICE, D.PROD_STATUS = S.PROD_NEWSTATUS
DELETE WHERE (D.PROD_STATUS = "OBSOLETE")
WHEN NOT MATCHED THEN
INSERT (PROD_ID, PROD_LIST_PRICE, PROD_STATUS)
VALUES (S.PROD_ID, S.PROD_NEW_PRICE, S.PROD_NEW_STATUS);
MERGE USING Product_Changes S -- Source/Delta table
INTO Products P -- Destination table 1
ON (P.PROD_ID = S.PROD_ID) -- Search/Join condition
WHEN MATCHED THEN UPDATE -- update if join
SET P.PROD_LIST_PRICE = S.PROD_NEW_PRICE
WHERE P.PROD_STATUS <> "OBSOLETE" -- Conditional
WHEN NOT MATCHED THEN
INSERT (PROD_ID, PROD_STATUS, PROD_LIST_PRICE) -- insert if not join
VALUES (S.PROD_ID, S.PROD_NEW_STATUS, S.PROD_NEW_PRICE)
WHERE S.PROD_STATUS <> "OBSOLETE";
Process
- First confirm that this is a correct oracle sql syntax, if not please ignore;
- Compare SQL definitions in Oficial SQL Doc and ShardingSphere SQL Doc;
- If there is any difference in ShardingSphere SQL Doc, please correct them by referring to the Official SQL Doc;
- Run mvn install the current_file_module;
- Check whether there are any exceptions. If indeed, please fix them. (Especially xxxVisitor.class);
- Add new corresponding SQL case in SQL Cases and expected parsed result in Expected Statment XML;
- Run SQLParserParameterizedTest to make sure no exceptions.
Relevant Skills
- Master JAVA language
- Have a basic understanding of Antlr
g4file - Be familiar with Oracle SQLs
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Hi, I searched the Oracle SQL Language Reference and found the following merge command descriptions, which seem to differ from the SQL syntax posted in the issue.
The documentation requires an INTO keyword, so perhaps we should check that the syntax of these SQL's is correct.
Hi @chakkk309, can you test these SQL with Oracle database? These case are obtained from the official website through crawlers, and they should be correct.
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Hi @strongduanmu , I checked these SQL statements on an Oracle database, and encountered the following error:
missing INTO keyword
Additionally, I found some examples on the Oracle website, such as:
The correct SQL should look like this:
MERGE INTO Products P
USING Product_Changes S
ON (P.PROD_ID = S.PROD_ID)
WHEN MATCHED THEN
UPDATE
SET P.PROD_LIST_PRICE = S.PROD_NEW_PRICE
WHERE P.PROD_STATUS <> "OBSOLETE";
MERGE INTO Products D2
USING New_Product S
ON (D2.PROD_ID = S.PROD_ID)
WHEN NOT MATCHED THEN
INSERT (PROD_ID, PROD_STATUS) VALUES (S.PROD_ID, S.PROD_NEW_STATUS);
MERGE INTO Products P
USING New_Product S
ON (1 = 0)
WHEN NOT MATCHED THEN
INSERT (PROD_ID, PROD_STATUS) VALUES (S.PROD_ID, S.PROD_NEW_STATUS);
MERGE INTO Products D
USING Product_Changes S
ON (D.PROD_ID = S.PROD_ID)
WHEN MATCHED THEN
UPDATE SET D.PROD_LIST_PRICE = S.PROD_NEW_PRICE, D.PROD_STATUS = S.PROD_NEWSTATUS
DELETE WHERE D.PROD_STATUS = "OBSOLETE"
WHEN NOT MATCHED THEN
INSERT (PROD_ID, PROD_LIST_PRICE, PROD_STATUS)
VALUES (S.PROD_ID, S.PROD_NEW_PRICE, S.PROD_NEW_STATUS);
MERGE INTO Products P
USING Product_Changes S
ON (P.PROD_ID = S.PROD_ID)
WHEN MATCHED THEN UPDATE
SET P.PROD_LIST_PRICE = S.PROD_NEW_PRICE
WHERE P.PROD_STATUS <> "OBSOLETE"
WHEN NOT MATCHED THEN
INSERT (PROD_ID, PROD_STATUS, PROD_LIST_PRICE)
VALUES (S.PROD_ID, S.PROD_NEW_STATUS, S.PROD_NEW_PRICE)
WHERE S.PROD_STATUS <> "OBSOLETE";
I tested these SQL statements, which are already supported by the PR https://github.com/apache/shardingsphere/pull/9361, https://github.com/apache/shardingsphere/pull/30452, and https://github.com/apache/shardingsphere/pull/28247, maybe we can close this issue.