MySQL

This page documents only how the python-fastapi-mysql target differs from python-fastapi-postgres. Everything not listed here — file tree, naming conventions, HTTP contract, OpenAPI, the FastAPI app/Docker app stage, extension points, limitations — is identical; read the PostgreSQL page for the full reference.

The database axis is a pluggable Dialect strategy (codegen/migration/Dialect.scala); it decides the SQLAlchemy column type, trigger shape, partial-index handling, and the connection / docker-compose wiring (DialectView). Selecting MySQL is one flag — no emitter or template changes.

sbt "cli/run compile --framework fastapi --db mysql --ignore-verify --out /tmp/out fixtures/spec/url_shortener.spec"

Deltas from PostgreSQL

• Compose service. The emitted docker-compose.yml provisions a mysql:8.4 database service (replacing the Postgres one); the migrations and app services wait on its healthcheck. The app container is otherwise unchanged.
• String columns. Unbounded string fields map to VARCHAR(255) rather than Postgres TEXT, since MySQL cannot index unbounded text without a key length.
• Column types. Remaining Postgres-specific types are mapped to their MySQL equivalents by the Dialect; the emitter is canonical.
• Test generation. No difference. --with-tests emits the full conformance / property / stateful suite here exactly as for PostgreSQL — the suite is dialect-invariant (black-box HTTP, ORM-based admin reset) and is byte-identical across every fastapi dialect.

CI gate

.github/workflows/python-build.yml runs the mysql matrix leg: it emits the project --with-tests, runs uv sync --all-extras, and performs an Alembic upgrade head → downgrade base → upgrade head round-trip against a real mysql:8.4 service — proving the --with-tests project generates, installs, and migrates on MySQL. The emitted suite is dialect-invariant — byte-identical across every fastapi dialect, asserted deterministically by TestEmitTest — so MySQL gets exactly the suite PostgreSQL does. (End-to-end execution of the generated app/suite is exercised by the nightly mutation job; it needs --with-synthesis to fill non-CRUD bodies and is independent of the database axis.)

If this page and the emitted output disagree, the emitter wins — file an issue or PR to correct the doc.