Oninit mysql-2-informix / MySQL wire proxy
Talk to an expert →

Solution Summary

Oninit® MySQL-2-Informix — MySQL Tools, Informix Data, No Application Change

Most teams running Informix end up running it alongside something else — a reporting application built against MySQL, an analytics tool that only speaks the MySQL wire, an ORM the development team already knows, an off-the-shelf product whose connector list ends at “MySQL 5+”. Bridging the gap usually means a parallel database, a brittle ETL, or a custom translator stuck onto the application stack.

Oninit® MySQL-2-Informix collapses that into a single small proxy. The application keeps speaking MySQL exactly as it does today, the data of record stays in Informix exactly where it is, and the translation surface is a documented, type-mapped, test-covered table.

What you get

  • Any standard MySQL client connects unchanged: mysql(1), JDBC, ODBC, the Connector/Python driver, an ORM, an existing application.
  • MySQL catalog statements answer correctly — SHOW DATABASES, SHOW TABLES, SHOW CREATE TABLE, SHOW INDEX, SHOW GRANTS, SHOW TRIGGERS.
  • MySQL CREATE TABLE just works: column types are translated to their Informix equivalents, the reverse is applied to SHOW CREATE TABLE, and ORM introspection sees what it expects.
  • Two interchangeable backends behind one config file — m2ie via the IBM Informix CSDK, or m2is in pure C with no CSDK on the deployment host.
  • Backed by Oninit, the team known across the Informix community as “the Down System Specialists.”

If your application speaks MySQL and your data lives in Informix, this is the shortest path between the two — without changing either side.

Talk to us

Call +1-913-732-8892 (US) or +44-2081-337529 (UK), or email support.info@oninit.com.

Next

See the full Features list, or the Type Mapping table that covers every MySQL column type the proxy translates to Informix.