Polyglot Runtime and Database Matrix
This page records an engineering verification snapshot from 2026-08-12. It is not the current seven-language capability tracker; use the TeaQL Conformance repository for ongoing runtime status and Latest Versions for today's generator selections and published package versions. It reports code that was generated, compiled, and executed against real databases. It does not infer support from the presence of a template, adapter, driver, or package name.
Some results were produced from validated development branches. A green cell therefore means verified in this snapshot, not necessarily available in the latest published package. It also does not define a commercial support lifetime or database-version SLA.
Database execution matrix
| Database | Java | Rust | Go | Python | C# / .NET | TypeScript |
|---|---|---|---|---|---|---|
| PostgreSQL | Verified | Verified | Verified | Verified | Verified | Verified |
| MySQL | Verified | Verified | Verified | Verified | Verified | Verified |
| SQLite | Verified | Verified | Verified | Verified | Verified | Verified |
| SQL Server | Verified | — | — | — | Verified | — |
| Oracle | Verified | — | — | — | — | — |
| DB2 | Verified | — | — | — | — | — |
| SAP HANA | Verified | — | — | — | — | — |
| DuckDB | Verified | — | — | — | — | — |
| DM8 / Dameng | Verified | — | — | — | — | — |
| Snowflake | Not executed | — | — | — | — | — |
— means that this verification campaign did not establish a real-database
result for that runtime/database pair. It is not a claim that implementation
is impossible.
Snowflake remains outside the verified set because no official Snowflake database server image suitable for local execution was found. A JDBC module or generated configuration alone is not counted as database evidence.
Runtime snapshot
| Runtime | Executed evidence | Verified databases | Important boundary |
|---|---|---|---|
| Java | 9 tests / 0 failures / 0 errors / 0 skipped | PostgreSQL, MySQL, SQLite, Oracle, DB2, DM8, SAP HANA, SQL Server, DuckDB | Android remains SQLite-only. |
| Rust | Generated API chain and runtime suite passed; runtime branch coverage reached 95.5%. | PostgreSQL, MySQL, SQLite | SQL Server is intentionally outside the current Rust scope. |
| Go | Runtime suite and generated SQL matrix passed; statement coverage reached 94.9%. | PostgreSQL, MySQL, SQLite | Includes generated-query WithComment compatibility. |
| Python | 73 runtime tests passed plus generated real-SQL integration. | PostgreSQL, MySQL, SQLite | These are real async SQL providers, not the earlier JSON/fake runtime. |
| C# / .NET | 124 runtime tests passed plus generated database integration. | PostgreSQL, MySQL, SQLite, SQL Server | SQL Server is verified only for Java and .NET in this snapshot. |
| TypeScript | 6 runtime tests plus 4 tests / 0 failures / 0 errors / 0 skipped in the generated matrix. | PostgreSQL, MySQL, SQLite | SQL providers are Node-only subpath exports; the browser/TFP root profile loads no database driver. |
What “verified” exercised
The generated integration tests did more than open a connection. For each green database combination in the generated matrix, the applicable test performed the following sequence:
- generate the language-specific domain library from the same parent/child model;
- compile or type-check the generated API with the real runtime;
- create or verify the database schema;
- create a parent entity and child entity through generated APIs;
- save the graph through an audited mutation;
- reconnect and query through intent-declared generated requests;
- verify the parent-child relationship;
- update the entity and verify optimistic version behavior;
- query the database directly to confirm row count and stored version.
The TypeScript matrix additionally verifies a contains filter, aggregate
query, and optimistic-conflict path. Its separate browser-profile probe proves
that importing the root package installs and loads none of pg, mysql2, or
better-sqlite3.
Java nine-database baseline
The Java matrix used:
| Item | Value |
|---|---|
| Timestamp | 2026-08-12T03:30:58+08:00 |
| Code generator commit | c7c9b2ef8f31353235fd2d8ec3a31c958bede71f |
| TeaQL Java commit | 265a0b98dc8e4389a1d3543696f5bfd850feeadd |
| Result | tests=9 failures=0 errors=0 skipped=0 |
| Test classes | JavaGeneratedPostgresIntegrationTest, JavaGeneratedMysqlSqliteIntegrationTest |
DM8 was tested in a dedicated container and data volume, bound only to the loopback interface. The existing shared DM8 container and its data directory were not modified.
TypeScript profile baseline
The Node SQL matrix used code generator commit
a8859208baadd5c78d237ea0633b575050b1973d, TeaQL TypeScript commit
08dbc09b6e169839278f3e1ee25677d82f662ef6, and Node v22.12.0. It completed
four generated tests with no failures, errors, or skips.
The browser-profile probe used TeaQL TypeScript commit
198356146093ee2567e16670f3865cc0bec2fe3a and confirmed:
- root import passed;
- installed database drivers: none;
- loaded database driver modules:
0; - root-entry SQL imports: none.
Evidence and reproduction
The preserved report excerpts, command shapes, and evidence boundaries are in Runtime Database Matrix Evidence — 2026-08-12.
The Java matrix is also exercised nightly by the maintained C300 database matrix runner. A later successful run should append a new dated record rather than silently rewriting this snapshot.
For the distinction between source presence, generated output, tested behavior, and maintained support, see Database Provider Compatibility.