GaussDB SQL Parser for Java
General SQL Parser (GSP) parses GaussDB 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 — GaussDB is available in the Java edition.
GaussDB SQL that GSP parses
EXECUTE DIRECT ON (dn_6001_6002)
'SELECT count(*) FROM tpcds.customer_address';Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvgaussdb);
parser.sqltext = sql; // the GaussDB SQL above
if (parser.parse() == 0) {
System.out.println(parser.sqlstatements.size() + " statement(s) parsed");
} else {
System.out.println(parser.getErrormessage());
}Java edition only. The .NET library has no GaussDB grammar, so this dialect cannot be parsed from C# or VB.NET. See the .NET SQL Parser SDK for the dialects it does cover.
What GSP handles in GaussDB
- MERGE INTO statements
- WITH RECURSIVE common table expressions
- PREPARE / EXECUTE prepared statements
- EXECUTE DIRECT ON distributed queries
- CREATE TYPE user-defined types and sequences
- Procedural SQL: GaussDB stored procedures and user-defined functions (CREATE PROCEDURE, CREATE FUNCTION), PL/SQL-style anonymous blocks, and CALL statements
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for GaussDB.
Recent GaussDB parser updates
- 2026-04-06 [GaussDB] Support EXECUTE DIRECT ON statement
- 2026-04-06 [GaussDB] Support SET LOCAL TRANSACTION and CREATE DIRECTORY
Full history in the release notes.
GaussDB resources
- GaussDB syntax reference — dialect documentation
- GaussDB keyword compatibility — every keyword, and whether it can be an identifier
- GaussDB capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
Common questions
Does GSP parse GaussDB stored procedures and procedural SQL?
Yes. GSP parses GaussDB stored procedures and user-defined functions (CREATE PROCEDURE, CREATE FUNCTION), PL/SQL-style anonymous blocks, and CALL statements 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 GaussDB database connection to validate SQL?
No. GSP validates GaussDB 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 GaussDB grammar?
GSP uses a dedicated hand-tuned grammar for GaussDB — not a generic SQL grammar with flags. The parser recognizes 584 GaussDB keywords and knows which 581 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the GaussDB parser from C# / .NET?
Not currently. GaussDB is a Java-edition dialect — the .NET library ships 15 dedicated grammars and GaussDB is not one of them, so there is no C# code path for it. Everything else on this page describes the Java SDK. If you need GaussDB in .NET, email info@sqlparser.com; customer demand is how dialects get prioritized for the .NET port.
Can GSP extract column-level lineage from GaussDB SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from GaussDB scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.