Progress OpenEdge SQL Parser for Java
General SQL Parser (GSP) parses Progress OpenEdge with a dedicated, hand-tuned grammar — full AST access, offline syntax validation, formatting, rewriting, and column-level data lineage. One commercial SDK — Progress OpenEdge is available in the Java edition.
Progress OpenEdge SQL that GSP parses
SELECT cust_num,
CASE region WHEN 'east' THEN 1 ELSE 0 END
FROM pub.customer;Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvopenedge);
parser.sqltext = sql; // the Progress OpenEdge 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 Progress OpenEdge 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 Progress OpenEdge
- OpenEdge data types
- CREATE VIEW
- CASE expressions
- OpenEdge literals
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for Progress OpenEdge.
Recent Progress OpenEdge parser updates
- 2026-01-11 Delegate ODBC and OpenEdge parsing to VendorParsers
- 2025-10-07 Migrate OpenEdge to modular architecture
Full history in the release notes.
Progress OpenEdge resources
- Progress OpenEdge syntax reference — dialect documentation
- Progress OpenEdge keyword compatibility — every keyword, and whether it can be an identifier
- Progress OpenEdge capability data (JSON) — measured construct-by-construct parse coverage, machine-readable
- Java quick start — Maven/Gradle setup and first parse
Common questions
Do I need a live Progress OpenEdge database connection to validate SQL?
No. GSP validates Progress OpenEdge 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 Progress OpenEdge grammar?
GSP uses a dedicated hand-tuned grammar for Progress OpenEdge — not a generic SQL grammar with flags. The parser recognizes 469 Progress OpenEdge keywords and knows which 427 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the Progress OpenEdge parser from C# / .NET?
Not currently. Progress OpenEdge is a Java-edition dialect — the .NET library ships 15 dedicated grammars and Progress OpenEdge 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 Progress OpenEdge in .NET, email info@sqlparser.com; customer demand is how dialects get prioritized for the .NET port.
Can GSP extract column-level lineage from Progress OpenEdge SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from Progress OpenEdge scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.