MySQL Parser for Java and .NET
General SQL Parser (GSP) parses MySQL with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage, including complete procedural SQL support. One commercial SDK, available for Java and .NET.
MySQL that GSP parses
CREATE PROCEDURE sync_totals()
BEGIN
DECLARE done INT DEFAULT 0;
UPDATE totals t JOIN orders o ON o.cid = t.cid SET t.amt = o.amt;
END Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvmysql);
parser.sqltext = sql; // the MySQL above
if (parser.parse() == 0) {
System.out.println(parser.sqlstatements.size() + " statement(s) parsed");
} else {
System.out.println(parser.getErrormessage());
} Parse it in C#
using gudusoft.gsqlparser;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvmysql);
parser.sqltext = sql; // the MySQL above
if (parser.parse() == 0)
{
Console.WriteLine(parser.sqlstatements.size() + " statement(s) parsed");
}
else
{
Console.WriteLine(parser.Errormessage);
} Same grammar, .NET-idiomatic API — properties instead of Java getters. See the C# quick start or the .NET SQL Parser SDK.
What GSP handles in MySQL
- Stored procedure blocks
- Cursors and loops
- LOAD DATA statements
- PREPARE/DEALLOCATE prepared statements
- SHOW and OPTIMIZE TABLE
- Procedural SQL: Stored procedures, functions, and triggers with DECLARE, cursors (OPEN/FETCH), and LOOP/REPEAT/WHILE control flow
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for MySQL.
Recent MySQL parser updates
- 2026-06-02 [MySQL] Degrade STRAIGHT_JOIN to INNER in semantic IR
- 2026-05-23 [PG, MSSQL, Snowflake, Oracle, MySQL] Admit UPDATE SET-RHS correlated scalar subqueries
- 2026-05-16 [MySQL] Self-reference DELETE admission
Full history in the release notes.
MySQL resources
- MySQL syntax reference — dialect documentation
- MySQL keyword compatibility — every keyword, and whether it can be an identifier
- MySQL capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
- C# quick start — .NET setup and first parse
Common questions
Does GSP parse MySQL stored procedures and procedural SQL?
Yes. GSP parses Stored procedures, functions, and triggers with DECLARE, cursors (OPEN/FETCH), and LOOP/REPEAT/WHILE control flow into a full AST — procedure bodies become real statement trees you can traverse, not opaque text blocks. This is what makes lineage and impact analysis work inside procedural code.
Do I need a live MySQL database connection to validate SQL?
No. GSP validates MySQL syntax completely offline. You get error line and column positions, the offending token, and a hint — with no server, driver, or credentials involved.
How complete is the MySQL grammar?
GSP uses a dedicated hand-tuned grammar for MySQL — not a generic SQL grammar with flags. The parser recognizes 538 MySQL keywords and knows which 534 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the MySQL parser from C# / .NET?
Yes. The .NET edition parses MySQL with the same grammar, and the API is idiomatic .NET rather than a Java transliteration: where Java has parser.getErrormessage() and stmt.getResultColumnList(), C# has parser.Errormessage and stmt.ResultColumnList. The package id is gudusoft.gsqlparser, multi-targeting net10.0 and netstandard2.0, so .NET Framework 4.6.2+ hosts are covered too.
Can GSP extract column-level lineage from MySQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from MySQL scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.