mysql-patterns

Topics in the source

• MySQL Patterns
• Activation
• Version Check
• Schema Defaults
• Indexing
• Query Patterns
• Upsert
• Keyset Pagination

Use this skill when working on MySQL or MariaDB schema design, migrations, slow-query investigation, queue-style transactions, connection pools, or production database configuration. Prefer exact version checks before applying a feature-specific pattern because MySQL and MariaDB have diverged in several SQL details. Designing MySQL or MariaDB tables, indexes, and constraints Reviewing migrations before they run on large production tables Debugging slow queries, lock waits, deadlocks, or connection exhaustion Adding keyset pagination, upserts, full-text search, JSON columns, or queues Configuring application connection pools, read replicas, TLS, or slow logs Start by identifying the engine and version: Keep MySQL and MariaDB guidance separate when syntax differs: MySQL documents row aliases as the replacement for VALUES(col) in ON DUPLICATE KEY UPDATE; VALUES(col) is deprecated there. MariaDB documents VALUES(col) as the supported way to reference inserted values in ON DUPLICATE KEY UPDATE; use it for cross-engine compatibility. SKIP LOCKED is appropriate for queue-like work only. It skips locked rows and can return an inconsistent view, so do not use it for general accounting or in

This is an excerpt. Refer to the complete source and its current requirements.