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

   # Background
   Hi community,
   
   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 openGauss SQL parsing in 
ShardingSphere.
   
   More details:
   
https://shardingsphere.apache.org/document/current/en/reference/sharding/parse/
   
   # Task
   This issue is to support more openGauss sql parse, as follows:
   ```sql
   rename user 
       user1 to user4, 
       user2 to user5,
       user3 to user6;
   ```
   
   ```sql
   SET [ SESSION | LOCAL ] ROLE role_name PASSWORD 'password';
   ```
   
   ```sql
    CREATE ROLE paul IDENTIFIED BY 'xxxxxxxxx';
   
   --设置当前用户为paul。
   
   ```
   
   ```sql
    SET ROLE paul PASSWORD 'xxxxxxxxx';
   
   --查看当前会话用户,当前用户。
   
   ```
   
   ```sql
   CREATE SCHEMA schema_name 
       [ [DEFAULT] CHARACTER SET | CHARSET [ = ] default_charset ] [ [DEFAULT] 
COLLATE [ = ] default_collation ];
   ```
   
   # Process
   1. First confirm that this is a correct openGauss sql syntax, if not please 
leave a message under the issue and ignore it;
   2. Compare SQL definitions in Official 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 Statement 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 openGauss 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