SQL dialect
Progress OpenEdge SQL Parser for Java and .NET
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, 38 dialects, Java and .NET.
Example
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());
}The .NET edition exposes the same API in C# — see the C# quick start.
Coverage
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.
Actively maintained
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.
Go deeper
Progress OpenEdge resources
- Progress OpenEdge syntax reference — dialect documentation
- Progress OpenEdge keyword compatibility — every keyword, and whether it can be an identifier
- Java quick start — Maven/Gradle setup and first parse
- C# quick start — NuGet setup for .NET
Common questions
Do I need a 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 424 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?
Yes. The .NET edition (NuGet package gudusoft.gsqlparser, .NET Standard 2.0) exposes the same API surface as the Java edition, so every Progress OpenEdge parsing feature on this page works in C# and VB.NET.
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.