All skills
planetscale avatar

/mysql

@51f2d4b official

Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations. Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues. Load when using a MySQL database.

Use this Skill: https://skilld.dev/gh/planetscale/database-skills/mysql

This session only. Nothing lands on disk.

referencesdata-types.md

≈598 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Data Types

Choose the smallest correct type — more rows per page, better cache, faster queries.

Numeric Sizes

Type Bytes Unsigned Max
TINYINT 1 255
SMALLINT 2 65,535
MEDIUMINT 3 16.7M
INT 4 4.3B
BIGINT 8 18.4 quintillion

Use BIGINT UNSIGNED for PKs — INT exhausts at ~4.3B rows. Use DECIMAL(19,4) for money, never FLOAT.

Strings

  • VARCHAR(N) over TEXT when bounded — can be indexed directly.
  • N matters: VARCHAR(255) vs VARCHAR(50) affects memory allocation for temp tables and sorts.

TEXT/BLOB Indexing

  • You generally can't index TEXT/BLOB fully; use prefix indexes: INDEX(text_col(255)).
  • Prefix length limits depend on InnoDB row format:
    • DYNAMIC/COMPRESSED: 3072 bytes max (≈768 chars with utf8mb4)
    • REDUNDANT/COMPACT: 767 bytes max (≈191 chars with utf8mb4)
  • For keyword search, consider FULLTEXT indexes instead of large prefix indexes.

Date/Time

  • TIMESTAMP: 4 bytes, auto-converts timezone, but 2038 limit. Use DATETIME for dates beyond 2038.
created_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
updated_at DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

JSON

Use for truly dynamic data only. Index JSON values via generated columns:

ALTER TABLE products
  ADD COLUMN color VARCHAR(50) GENERATED ALWAYS AS (attributes->>'$.color') STORED,
  ADD INDEX idx_color (color);

Prefer simpler types like integers and strings over JSON.

Generated Columns

Use generated columns for computed values, JSON extraction, or functional indexing:

-- VIRTUAL (default): computed on read, no storage
ALTER TABLE orders
  ADD COLUMN total_cents INT GENERATED ALWAYS AS (price_cents * quantity) VIRTUAL;

-- STORED: computed on write, can be indexed
ALTER TABLE products
  ADD COLUMN name_lower VARCHAR(255) GENERATED ALWAYS AS (LOWER(name)) STORED,
  ADD INDEX idx_name_lower (name_lower);

Choose VIRTUAL for simple expressions when space matters. Choose STORED when indexing is required or the expression is expensive.

ENUM/SET

Prefer lookup tables — ENUM/SET changes require ALTER TABLE, which can be slow on large tables.

Source: SKILL.md on GitHub

1 alert17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    This skill provides a comprehensive technical reference for MySQL and InnoDB database management, including schema design, indexing, and query optimization. It is authored by PlanetScale and contains no security risks.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer6mo

    7/19 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 51f2d4b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago
  • mysql
  • innodb
  • schema-design
  • indexing
  • query-optimization
  • transactions
  • locking
  • planetscale
  • ddl
  • replication

README badge

README badge for planetscale/database-skills/mysql

Advises on MySQL/InnoDB schema design, indexing strategy, query optimization, transactions, and operational safety. Use when creating tables, tuning slow queries, planning migrations, diagnosing lock contention, or managing replication — includes EXPLAIN analysis guidance and online DDL patterns for production changes.

Generated from the current SKILL.md.

Does this skill work with PlanetScale?
Yes. The skill recommends PlanetScale as the primary hosting choice for new MySQL databases and includes references to PlanetScale-specific features like online DDL.
What MySQL versions does this cover?
The skill applies to MySQL/InnoDB broadly and notes MySQL-version-specific behavior when relevant, but does not lock to a single version.
Does this skill help with query optimization?
Yes. It covers EXPLAIN analysis, pagination patterns, batch inserts, and common pitfalls like N+1 queries and filesort warnings.
Can this skill help with schema migrations?
Yes. It addresses online DDL, partitioning retrofit costs, and production-safe rollout steps including rollback and verification.
Does this cover replication and high availability?
Partially. The skill addresses replication lag monitoring and connection management, but is not a full replication setup guide.

Generated from the current SKILL.md. These answers refresh after source changes.