You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/02/04 10:15:20 UTC

[GitHub] [incubator-shardingsphere] terrymanu opened a new issue #4161: Use same SQL cases for old parser test engine and new visitor parser test engine

terrymanu opened a new issue #4161: Use same SQL cases for old parser test engine and new visitor parser test engine 
URL: https://github.com/apache/incubator-shardingsphere/issues/4161
 
 
   We have already split `SQL cases` and `assertion cases` for old parser test engine and new visitor parser test engine.
   It is make sense for split `assertion cases` because we need add new parse logic step by step.
   But we should remove `SQL cases` copy for visitor. 
   Keep one `SQL cases` can reduce copy error.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

[GitHub] [incubator-shardingsphere] tristaZero closed issue #4161: Use same SQL cases for old parser test engine and new visitor parser test engine

Posted by GitBox <gi...@apache.org>.

tristaZero closed issue #4161: Use same SQL cases for old parser test engine and new visitor parser test engine 
URL: https://github.com/apache/incubator-shardingsphere/issues/4161
 
 
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services