SQL is relatively simple compared to other programming languages, but it is still a complete set of programming language, so there is no essential difference between parsing SQL grammar and parsing other languages (Java, C and Go, etc.).
The parsing process can be divided into lexical parsing and syntactic parsing. Lexical parser is used to divide SQL into indivisible atomic signs, i.e., Token. According to the dictionary provided by different database dialect, it is categorized into keyword, expression, literal and operator. SQL is then converted into abstract syntax tree by syntactic parser.
For example, the following SQL:
SELECT id, name FROM t_user WHERE status = 'ACTIVE' AND age > 18
Its AST(Abstract Syntax Tree) after parsing is as:
To better understand, the Token of abstract syntax tree keywords is shown in green; that of variables is shown in red; what’s to be further divided is shown in grey.
At last, through traversing the abstract syntax tree, the context needed by sharding is extracted and the place that may need to be rewritten is also marked out. Parsing context for the use of sharding includes select items, table information, sharding conditions, auto-increment primary key information, Order By information, Group By information, and pagination information (Limit, Rownum and Top). One-time parsing process of SQL is irreversible, each Token is parsed according to the original order of SQL with a high performance. Considering similarities and differences between SQL of all kinds of database dialect, SQL dialect dictionaries of different types of databases are provided in the parsing module.
As the core of database sharding and table sharding, SQL parser takes the performance and compatibility as its most important index. ShardingSphere SQL parser has undergone the upgrade and iteration of 3 generations of products.
To pursue good performance and quick achievement, the first generation of SQL parser uses
Druid before 1.4.x version.
As tested in practice, its performance exceeds other parsers a lot.
The second generation of SQL parsing engine begins from 1.5.x version, ShardingSphere has adopted fully self-developed parsing engine ever since.
Because of different purposes, ShardingSphere does not need to transform SQL into a totally abstract syntax tree or traverse twice through visitor.
half parsing method, it only extracts the context required by data sharding, so the performance and compatibility of SQL parsing is further improved.
The third generation of SQL parsing engine begins from 3.0.x version.
ShardingSphere tries to adopts ANTLR as the SQL parsing engine, and plans to replace the former parsing engine according to the order of
DDL -> TCL -> DAL –> DCL -> DML –>DQL.
It is still in the process of replacement and iteration.
Hoping for a better compatibility with SQL, we use ANTLR in the parsing engine of ShardingSphere.
Though complex expressions, recursions, sub-queries and other sentences are not focused by the sharding core of ShardingSphere, they can influence the friendliness to understand SQL.
After testing in actual cases, the performance of ANTLR is about 3-10 times slower than the self-developed parsing engine when parsing SQL.
To compensate for this gap, ShardingSphere will use the SQL parsing tree of
PreparedStatement to put in the cache.
PreparedStatement is recommended to be used as the pre-compile method to improve the performance.
The overall structure division of the third generation of SQL parsing engine is shown in the following picture.