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, available for Java and .NET.

82%
of 164 documented IBM Informix constructs parse fully — measured on GSP 4.1.10 (2026-08-08)
703
IBM Informix keywords recognized by the grammar
674
keywords the parser also accepts as identifiers
80
IBM Informix test SQL files in the regression corpus
Weekly
release cadence — dialect fixes ship in days

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());
}

Parse it in C#

using gudusoft.gsqlparser;

TGSqlParser parser = new TGSqlParser(EDbVendor.dbvinformix);
parser.sqltext = sql; // the IBM Informix SQL 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 IBM Informix

Beyond parsing, the same AST powers table/column extraction, validation, formatting, and column-level lineage for IBM Informix.

Recent IBM Informix parser updates

Full history in the release notes.

IBM Informix resources

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 live 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 674 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 parses IBM Informix 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 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.