FlyingZC opened a new issue, #26972:
URL: https://github.com/apache/shardingsphere/issues/26972

   # 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:
   ```sql
   ALTER PROFILE default LIMIT
    PASSWORD_VERIFY_FUNCTION verify_function_11G;
   ```
   
   ```sql
   ALTER PROFILE new_profile 
      LIMIT PASSWORD_REUSE_TIME 90 
      PASSWORD_REUSE_MAX UNLIMITED;
   ```
   
   ```sql
   ALTER ROLLBACK SEGMENT rbs_one 
      SHRINK TO 100M;
   ```
   
   ```sql
   ALTER ROLLBACK SEGMENT rbs_one ONLINE;
   ```
   
   ```sql
   ALTER PROFILE default LIMIT IDLE_TIME  2;
   ```
   
   # Process
   1. First confirm that this is a correct oracle sql syntax, if not please 
ignore;
   2. Compare SQL definitions in Oficial SQL Doc and ShardingSphere SQL Doc;
   3. If there is any difference in ShardingSphere SQL Doc, please correct them 
by referring to the Official SQL Doc;
   4. Run mvn install the current_file_module;
   5. Check whether there are any exceptions. If indeed, please fix them. 
(Especially xxxVisitor.class);
   6. Add new corresponding SQL case in SQL Cases and expected parsed result in 
Expected Statment XML;
   7. Run SQLParserParameterizedTest to make sure no exceptions.
   
   # Relevant Skills
   1. Master JAVA language
   2. Have a basic understanding of Antlr `g4` file
   3. Be familiar with Oracle SQLs


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to