SQL dialect
IBM Informix SQL Parser for Java and .NET
General SQL Parser (GSP) parses IBM Informix 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, 38 dialects, Java and .NET.
Example
IBM Informix SQL that GSP parses
CREATE PROCEDURE raise_pay(emp_id INT, pct DECIMAL(5,2))
UPDATE employee SET salary = salary * (1 + pct / 100)
WHERE id = emp_id;
END PROCEDURE;Parse it in Java
import gudusoft.gsqlparser.*;
TGSqlParser parser = new TGSqlParser(EDbVendor.dbvinformix);
parser.sqltext = sql; // the IBM Informix 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 IBM Informix
- SPL procedures and functions
- CREATE ROW TYPE
- Collection queries
- EXECUTE IMMEDIATE
- ALTER FRAGMENT
- Procedural SQL: SPL stored procedures, functions, and triggers, including EXECUTE PROCEDURE/FUNCTION and EXECUTE IMMEDIATE
Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for IBM Informix.
Actively maintained
Recent IBM Informix parser updates
- 2026-06-02 [Informix] Carry column list on table-level PRIMARY KEY
- 2026-01-11 Delegate Impala and Informix parsing to VendorParsers
- 2025-10-07 Migrate Informix to modular architecture
Full history in the release notes.
Go deeper
IBM Informix resources
- IBM Informix syntax reference — dialect documentation
- IBM Informix 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
Does GSP parse IBM Informix stored procedures and procedural SQL?
Yes. GSP parses SPL stored procedures, functions, and triggers, including EXECUTE PROCEDURE/FUNCTION and EXECUTE IMMEDIATE 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 IBM Informix database connection to validate SQL?
No. GSP validates IBM Informix 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 IBM Informix grammar?
GSP uses a dedicated hand-tuned grammar for IBM Informix — not a generic SQL grammar with flags. The parser recognizes 703 IBM Informix keywords and knows which 659 of them can also be used as identifiers, which is exactly the kind of edge case that breaks generic parsers.
Can I use the IBM Informix 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 IBM Informix parsing feature on this page works in C# and VB.NET.
Can GSP extract column-level lineage from IBM Informix SQL?
Yes. The built-in DataFlowAnalyzer produces column-level lineage, impact analysis, and call graphs from IBM Informix scripts — it is the engine behind Gudu SQLFlow and the lineage integrations for DataHub and OpenMetadata.