Create and migrate SQLite and MySQL schemas with Drizzle ORM.
npx skills add https://github.com/recca0120/code-quest --skill drizzle-orm-recca0120
Please help me install this Agent Skill. Skill: drizzle-orm Source: https://github.com/recca0120/code-quest/tree/main/.claude/skills/drizzle-orm Command: npx skills add https://github.com/recca0120/code-quest --skill drizzle-orm-recca0120
Drizzle ORM patterns prevent schema drift and migration mistakes when you need to support multiple SQL dialects (SQLite and MySQL) in the same application.
Use Case: You are adding new session fields and raw-event tables to support persisted session management and event append/query in a web server that can run on SQLite locally and MySQL in production.
Add or update schema definitions under apps/server/src/db for the target dialect, ensure shared column names stay in sync, then run migrations for both SQLite and MySQL and verify schema consistency with the test that checks table columns.
High-intent search queries and answers about installing and using this skill.
To maintain consistent database schemas across SQLite and MySQL using Drizzle ORM, you define equivalent table definitions per dialect while sharing common column naming constants. This prevents schema drift by ensuring column alignment across different SQL dialects.
The best way to generate separate migrations for SQLite and MySQL is to use dialect-scoped migration generation. This workflow allows you to create and run distinct migrations per dialect, preventing migration mistakes when supporting multiple SQL environments.
You verify schema consistency between SQL dialects by writing schema consistency tests that check table columns. These tests validate that dialect-specific tables still match the intended column sets, ensuring shared column names stay in sync across environments.
Yes, you can use drizzle-zod with better-sqlite3 and mysql2 clients in the same application. The setup requires dialect-specific clients for each environment, allowing you to run SQLite locally and MySQL in production while sharing schema definitions.
You need shared column constants when defining tables and relations to prevent schema drift across SQLite and MySQL. Keeping equivalent table definitions in sync ensures that dialect-specific tables match the intended column sets during multi-environment deployments.
To implement repository patterns with Drizzle ORM for multi-environment deployments, you define tables and relations using shared column constants and dialect-specific clients. This setup supports consistent data access whether running SQLite locally or MySQL in production.
contatomayconBuild type-safe SQL data-access layers with compile-time query inference.
wyattowalshDesign, generate, and validate SQL schemas and migrations across PostgreSQL, MySQL, and SQLite.
raulnqManage database schema changes and Drizzle ORM migrations for TypeScript projects.
duanbiao2000Migrate database schemas and data across Sequelize, TypeORM, and Prisma.
