Skip to main content

Rust First Verification

Run the shared School SQLite example from a checkout of teaql-io-site:

npm run verify:school -- --language rust

The complete Rust application uses the same School model as the other six runtimes. The runner generates and builds the workspace, checks root/constant bootstrap twice, saves a school with an audit reason, then starts a new process to read it back. An independent SQLite checker verifies persisted fields and relationships after every phase. Logs, exit codes and row snapshots are retained under artifacts/school/.

Verify the generated application in this order:

  1. Record the generator, cargo-teaql, emitted runtime, Rust toolchain, and provider versions.
  2. Build and test the generated library and application without generated-file edits.
  3. Install the Runtime Module and call context-scoped ensure_schema explicitly.
  4. Repeat schema setup and prove root/constant bootstrap is idempotent.
  5. Execute a bounded query with non-empty comment and purpose.
  6. Perform an audited create/update and read the persisted entity back.
  7. Exercise Checker/Fix before provider mutation and verify optimistic conflict behavior.
  8. Regenerate after a model change and review the diff.

Use Cross-language Conformance Status for the current evidence vocabulary and the Rust Compatibility Archive only for its dated campaign. Keep SQLite, PostgreSQL, MySQL, search, memory, local-source, and released-package evidence separate.

Continue with Rust Business Scenarios.