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 2019/12/07 13:20:24 UTC

[GitHub] [incubator-shardingsphere] SteNicholas commented on issue #3676: Is there any good way to handle with parsing sql first time, which is taking too many time?

SteNicholas commented on issue #3676: Is there any good way to handle with parsing sql first time, which is taking too many time?
URL: https://github.com/apache/incubator-shardingsphere/issues/3676#issuecomment-562850778
 
 
   > I have readed the document before and knew ANTLR is slow. Our project has hundreds SQL, and many SQL like 'select...in (...)' or 'insert...values(...)',and the number of parameters is different, so it has thousands different situations. It is impractical to preheat so many SQL (preheat every SQL need serval seconds). So any other way to handle with it?
   > 
   > I think if the SQL contain the table which need sharding or encrypt some column, it can parse SQL by ANTLR, but for other table, maybe it is not need parse by ANTLR but with druid, or others. Or is there any more elegant way complete it?
   
   Why no need to parse by Antlr? Could you give the performance about the comparsion among the parse engine you mentioned above?

----------------------------------------------------------------
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