Runtime Database Matrix Evidence — 2026-08-12

This page preserves the concise, non-secret output of the 2026-08-12 verification campaign. Credentials, container environment variables, and full runner logs are deliberately not published.

Evidence contract

The campaign counts a database only when generated code and the real runtime complete an end-to-end persistence test. Merely compiling a provider, loading a driver, or finding a runtime module is insufficient.

Every database test is isolated to test tables or a dedicated database/data volume. The runner may start existing test containers when needed and stops only containers that it started. It does not delete business data.

Java report excerpt

# TeaQL Java database matrix evidence

- Timestamp: 2026-08-12T03:30:58+08:00
- Codegen commit: c7c9b2ef8f31353235fd2d8ec3a31c958bede71f (clean)
- TeaQL Java commit: 265a0b98dc8e4389a1d3543696f5bfd850feeadd
- Result: tests=9 failures=0 errors=0 skipped=0
- Databases: PostgreSQL, MySQL, SQLite, Oracle, DB2, DM8,
  SAP HANA, SQL Server, DuckDB
- Snowflake: skipped because no official local Snowflake database server
  image is available.

The source test entry points were:

JavaGeneratedPostgresIntegrationTest
JavaGeneratedMysqlSqliteIntegrationTest

The second class contains explicit methods for MySQL, SQLite, Oracle, DB2, DM8, SAP HANA, SQL Server, and DuckDB. PostgreSQL remains a separate test class. The combined Surefire XML result produced the nine-test summary above.

TypeScript SQL report excerpt

# TeaQL TypeScript database matrix evidence

- Timestamp: 2026-08-12T02:58:55+08:00
- Codegen commit: a8859208baadd5c78d237ea0633b575050b1973d (clean)
- teaql-ts commit: 08dbc09b6e169839278f3e1ee25677d82f662ef6 (clean)
- Node: v22.12.0
- Result: tests=4 failures=0 errors=0 skipped=0
- Databases: PostgreSQL, MySQL, SQLite
- Coverage: schema creation, generated API compilation, parent-child cascade
  save, reconnect query, contains filter, optimistic version update/conflict,
  aggregate query, and direct database verification.

TypeScript browser-profile report excerpt

# TeaQL TypeScript browser profile evidence

- Timestamp: 2026-08-12T03:05:15+08:00
- teaql-ts commit: 198356146093ee2567e16670f3865cc0bec2fe3a
- Node: v22.12.0
- Install: default npm install of teaql-ts
- Root import: passed
- Installed database drivers: none
- Loaded database driver modules: 0
- Root entry SQL imports: none

This separate probe matters because a full-stack TypeScript runtime should not force browser applications to install native or server-only SQL drivers. SQL is exposed through explicit Node subpaths instead.

Other runtime entry points

The same code generator branch retains database test entry points for the other generated runtimes:

Runtime	Generated integration methods
Python	generatedPythonWorkspacePersistsTaskGraphToPostgres, ...ToMysql, ...ToSqlite
Go	generatedGolangWorkspacePersistsTaskGraphToPostgres, ...ToMysql, ...ToSqlite
C# / .NET	generatedDotnetWorkspacePersistsTaskGraphToPostgres, ...ToMysql, ...ToSqlite, ...ToSqlServer
TypeScript	generatedTypescriptWorkspacePersistsTaskGraphToPostgres, ...ToMysql, ...ToSqlite

The consolidated runtime results retained for this campaign were:

Runtime	Result retained with the campaign
Rust	Generated API/database chain passed for PostgreSQL, MySQL, and SQLite; runtime branch coverage 95.5%.
Go	Generated three-database matrix passed; runtime statement coverage 94.9%; SelectQuery.WithComment compatibility included.
Python	Generated three-database matrix passed; 73 runtime tests passed using real async SQL providers.
C# / .NET	Generated PostgreSQL, MySQL, SQLite, and SQL Server matrix passed; 124 runtime tests passed.

These consolidated rows establish the dated engineering snapshot. They do not replace per-runtime CI artifacts or define a released-package support policy.

Command shape

The Java matrix runner installs the matching TeaQL Java modules, exports database connection variables from the isolated test environment, and runs:

mvn -q -pl generator -am \
  -Dteaql.generated.java.version=17 \
  -Dtest=JavaGeneratedPostgresIntegrationTest,JavaGeneratedMysqlSqliteIntegrationTest \
  -Dsurefire.failIfNoSpecifiedTests=false \
  test

Language-specific generated test classes use their normal toolchains: Cargo, Go, Python/pytest, .NET, and Node/npm. Database credentials belong in the runner environment and must never be committed to documentation.

Interpreting this record

• Verified means the generated API path reached and was checked against a real database.
• Not executed means this campaign lacks runtime evidence.
• Supported should be used only after maintainers publish version ranges, maintenance policy, and lifecycle commitments.

Return to the current Polyglot Runtime and Database Matrix.