MySQL¶

Scythe supports MySQL/MariaDB with dialect-specific type handling across all 10 languages. MySQL support operates at the parser and analyzer level -- SQL parsing, type inference, and nullability analysis are fully MySQL-aware. The code generation backends work the same regardless of the source database.

Backend support¶

Every language has at least one MySQL backend. Multi-engine backends (like java-jdbc, php-pdo, rust-sqlx) load engine-specific manifests automatically.

Differences from PostgreSQL¶

AUTO_INCREMENT handling¶

CREATE TABLE users (
    id INT AUTO_INCREMENT PRIMARY KEY,
    name VARCHAR(255) NOT NULL
);

AUTO_INCREMENT columns are treated as NOT NULL, equivalent to PostgreSQL's SERIAL.

Inline ENUM¶

MySQL enums are declared inline on the column:

CREATE TABLE users (
    id INT AUTO_INCREMENT PRIMARY KEY,
    status ENUM('active', 'inactive', 'banned') NOT NULL
);

These map to string in the neutral type system. There is no separate enum:: resolution for inline MySQL enums.

Placeholder handling¶

MySQL uses ? positional placeholders. Scythe translates $N in your SQL to ? for MySQL backends:

-- Written as:
SELECT id, name FROM users WHERE id = $1;

-- Translated to:
SELECT id, name FROM users WHERE id = ?;

Type mapping table¶