ericrisco/rsc-harness / skills/mysql
mysql
VerifiedUse when designing, querying, indexing or operating a MySQL or MariaDB database and engine-specific behaviour matters — schema and type choices, index design, reading EXPLAIN, online schema change, replication and replica lag, locking and InnoDB deadlocks, charset traps, and server config. NOT portable SELECT/JOIN/window-function craft (that is `sql`), NOT PostgreSQL engine behaviour like VACUUM or JSONB (that is `postgresdb`), NOT the PlanetScale/Vitess branch-and-deploy workflow (that is `planetscale`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.7 KB |
| evals/README.md | markdown | 983 B |
| evals/cases.yaml | config | 3.5 KB |
| references/indexing-and-explain.md | markdown | 7.3 KB |
| references/mysql-vs-mariadb.md | markdown | 4.6 KB |
| references/online-ddl-and-migrations.md | markdown | 5.9 KB |
| references/replication-and-ha.md | markdown | 5.5 KB |
| scripts/verify.shexecutable | script | 6.6 KB |
references/mysql-vs-mariadb.md
View on GitHub# MySQL vs MariaDB divergence
MariaDB began as a MySQL fork and the two have diverged enough that copy-pasted SQL, auth setup, and
operational assumptions break across them. Always know *which* engine the project runs before you
answer. This is the depth behind the small table in `SKILL.md`.
## Versions and support
| | MySQL | MariaDB |
|---|---|---|
| Current LTS | **8.4 LTS** (GA 2024-04-30, supported through April 2032) | **11.8 LTS** (2025 yearly LTS) |
| Innovation / short-cycle | **9.x** (9.0 GA 2024-07-01, …, 9.4.0 2025-07-22) | rolling releases between LTS years |
| Owner | Oracle | MariaDB Foundation / MariaDB plc |
MariaDB version numbers do **not** track MySQL's — MariaDB 11.8 is not "MySQL 11". Feature parity is
partial and one-directional in places (MariaDB has features MySQL lacks and vice versa).
## Authentication
| | MySQL 8.4 / 9.x | MariaDB 11.8 |
|---|---|---|
| Default plugin | `caching_sha2_password` (SHA-256, server-side cache; TLS for first auth) | `mysql_native_password` and `ed25519` |
| `mysql_native_password` | Disabled by default in 8.4, **removed in 9.0** | Still a first-class plugin |
This is the most common cross-engine connection failure: a client/driver configured for MariaDB's
native auth hits a MySQL 8.4 server and gets *"Authentication plugin caching_sha2_password cannot be
loaded"* — fix is a `caching_sha2_password`-aware client over TLS, not re-enabling the old plugin.
## Vector search — NOT drop-in compatible
Both engines added native vector search, but with **incompatible syntax**:
| | MySQL 9.0+ (Innovation only) | MariaDB 11.8 (LTS) |
|---|---|---|
| Type | `VECTOR(n)` — 4-byte floats, default max 2048, max 16383 entries | `VECTOR(n)` |
| Parse / format | `STRING_TO_VECTOR()` / `TO_VECTOR()`, `VECTOR_TO_STRING()` / `FROM_VECTOR()` | `VEC_FromText()` / `VEC_ToText()` |
| Distance | distance functions per the 9.x line | `VEC_DISTANCE_EUCLIDEAN()`, `VEC_DISTANCE_COSINE()`, `VEC_DISTANCE()` |
| Acceleration | — | SIMD (AVX2/AVX512/ARM/Power10) |
| Key constraint | A `VECTOR` column **cannot be any kind of key** (no PK/FK/UK/partition) | indexable for approximate search |
| LTS availability | **Not in 8.4 LTS** — Innovation 9.x only | In the 11.8 LTS line |
If a project needs vector search on a conservative LTS today, MariaDB 11.8 has it in LTS; MySQL only
has it on the short-lived 9.x Innovation track. The SQL is not portable between them — pick one and
write to its functions.
## Snapshot isolation
MariaDB 11.8 ships `innodb_snapshot_isolation` defaulting **ON**, which makes a `REPEATABLE READ`
transaction *detect write conflicts* (raising an error instead of silently applying a stale-snapshot
write). Stock MySQL `REPEATABLE READ` does **not** do this — it gives a consistent snapshot but no
write-conflict detection. Code that relies on MariaDB raising a conflict error will silently succeed
(and possibly lose an update) on MySQL, and vice versa code that doesn't expect the error will fail
on MariaDB.
## Other SQL surface divergences
| Feature | MySQL | MariaDB |
|---|---|---|
| `RETURNING` | `INSERT ... RETURNING` only (8.0+) | `INSERT` / `UPDATE` / `DELETE ... RETURNING` |
| Sequences | No `CREATE SEQUENCE` (use `AUTO_INCREMENT`) | `CREATE SEQUENCE` supported |
| System-versioned (temporal) tables | Not supported | `WITH SYSTEM VERSIONING` + `FOR SYSTEM_TIME` queries |
| `JSON` type | Native binary `JSON` | Historically a `LONGTEXT` alias with JSON functions; check the version — behaviour and storage differ |
| Optimizer / hints | Oracle-style optimizer, `/*+ HINT */` hint syntax, hypergraph optimizer in newer Innovation | Different optimizer, different hint set and defaults; plans differ for the same query |
| Storage engines | InnoDB-centric | InnoDB plus Aria, ColumnStore, Spider, etc. |
## Migration gotchas, both directions
- **MariaDB → MySQL**: drop reliance on sequences, system-versioned tables, multi-statement
`RETURNING`, and the snapshot-isolation conflict behaviour. Re-check JSON columns. Re-key any
vector columns and rewrite vector SQL.
- **MySQL → MariaDB**: auth changes (native/ed25519 vs caching_sha2_password); rewrite MySQL 9
vector SQL to `VEC_*`; expect `innodb_snapshot_isolation=ON` to start raising conflict errors your
app didn't see before; verify optimizer-hint syntax and re-test query plans.
- **Don't trust `mysqldump` round-trips blindly** across engines — types, charsets, and engine
clauses can differ. Dump, then read the DDL before loading into the other engine.
Bottom line: treat MySQL and MariaDB as two different databases that happen to share a wire protocol
and a lot of grammar. Confirm the engine, then write to its specifics.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |