Database Design

MoizIbnYousaf/ai-agent-skills/skills/database-design

作者 MoizIbnYousaf6d95c788aa22ce39a4807b9a4c31c758a2036dc6MIT收錄於 2026年10月9日更新於 2026年10月9日

Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases. Use for designing schemas, writing migrations, or optimizing queries.

AI 產生的概覽

用於設計資料庫結構、索引、遷移與查詢最佳化的參考指南。

功能
提供以 SQL 為主的參考資料,涵蓋結構設計,包括正規化與反正規化模式、索引類型以及索引使用情形分析查詢。也涉及遷移模式(例如交易式遷移與零停機遷移)、使用 EXPLAIN 分析的查詢最佳化,以及確保資料完整性的條件約束。交付內容是指導說明與範例 SQL,而非產生的檔案或執行的指令碼。
適用情境
適用於設計關聯式或 NoSQL 結構、撰寫或審查遷移,以及調校慢速查詢的情境。適合需要權衡索引策略、條件約束或遷移安全性的 PostgreSQL 與 MySQL 工作。
執行需求
未隨附指令碼或工具,僅有說明文件與 SQL 範例。套用這些指導需要可存取 PostgreSQL 或 MySQL 等資料庫,以及用來執行範例查詢的用戶端。

Database Design

Schema Design Principles

Normalization Guidelines

sql
-- 1NF: Atomic values, no repeating groups-- 2NF: No partial dependencies on composite keys-- 3NF: No transitive dependencies
-- Users table (normalized)CREATE TABLE users (  id SERIAL PRIMARY KEY,  email VARCHAR(255) UNIQUE NOT NULL,  created_at TIMESTAMPTZ DEFAULT NOW());
-- Addresses table (separate entity)CREATE TABLE addresses (  id SERIAL PRIMARY KEY,  user_id INTEGER REFERENCES users(id) ON DELETE CASCADE,  street VARCHAR(255),  city VARCHAR(100),  country VARCHAR(100),  is_primary BOOLEAN DEFAULT false);

Denormalization for Performance

sql
-- When read performance matters more than write consistencyCREATE TABLE order_summaries (  id SERIAL PRIMARY KEY,  order_id INTEGER REFERENCES orders(id),  customer_name VARCHAR(255),  -- Denormalized from customers  total_amount DECIMAL(10,2),  item_count INTEGER,  last_updated TIMESTAMPTZ DEFAULT NOW());

Index Design

Common Index Patterns

sql
-- B-tree (default) for equality and range queriesCREATE INDEX idx_users_email ON users(email);
-- Composite index (order matters!)CREATE INDEX idx_orders_user_date ON orders(user_id, created_at DESC);
-- Partial index for specific conditionsCREATE INDEX idx_active_users ON users(email) WHERE deleted_at IS NULL;
-- GIN index for array/JSONB columnsCREATE INDEX idx_posts_tags ON posts USING GIN(tags);
-- Covering index (includes additional columns)CREATE INDEX idx_orders_covering ON orders(user_id) INCLUDE (total, status);

Index Analysis

sql
-- Check index usageSELECT  schemaname, tablename, indexname,  idx_scan, idx_tup_read, idx_tup_fetchFROM pg_stat_user_indexesORDER BY idx_scan DESC;
-- Find missing indexesSELECT  relname, seq_scan, seq_tup_read,  idx_scan, idx_tup_fetchFROM pg_stat_user_tablesWHERE seq_scan > idx_scanORDER BY seq_tup_read DESC;

Migration Patterns

Safe Migration Template

sql
-- Always use transactionsBEGIN;
-- Add column with default (non-blocking in PG 11+)ALTER TABLE users ADD COLUMN status VARCHAR(20) DEFAULT 'active';
-- Create index concurrently (doesn't lock table)CREATE INDEX CONCURRENTLY idx_users_status ON users(status);
-- Backfill data in batchesUPDATE users SET status = 'active' WHERE status IS NULL AND id BETWEEN 1 AND 10000;
COMMIT;

Zero-Downtime Migrations

1. Add new column (nullable)2. Deploy code that writes to both columns3. Backfill old data4. Deploy code that reads from new column5. Remove old column

Query Optimization

EXPLAIN Analysis

sql
-- Always use EXPLAIN ANALYZEEXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)SELECT * FROM orders WHERE user_id = 123 AND status = 'pending';
-- Key metrics to watch:-- - Seq Scan vs Index Scan-- - Actual rows vs Estimated rows-- - Buffers: shared hit vs read

Common Optimizations

sql
-- Use EXISTS instead of IN for large setsSELECT * FROM users uWHERE EXISTS (SELECT 1 FROM orders o WHERE o.user_id = u.id);
-- Pagination with keyset (cursor) instead of OFFSETSELECT * FROM postsWHERE created_at < '2024-01-01'ORDER BY created_at DESCLIMIT 20;
-- Use CTEs for complex queriesWITH active_users AS (  SELECT id FROM users WHERE last_login > NOW() - INTERVAL '30 days')SELECT * FROM orders WHERE user_id IN (SELECT id FROM active_users);

Constraints & Data Integrity

sql
-- Primary keyALTER TABLE users ADD PRIMARY KEY (id);
-- Foreign key with cascadeALTER TABLE orders ADD CONSTRAINT fk_orders_user  FOREIGN KEY (user_id) REFERENCES users(id) ON DELETE CASCADE;
-- Check constraintALTER TABLE products ADD CONSTRAINT chk_price_positive  CHECK (price >= 0);
-- Unique constraintALTER TABLE users ADD CONSTRAINT uniq_users_email UNIQUE (email);
-- Exclusion constraint (no overlapping ranges)ALTER TABLE reservations ADD CONSTRAINT excl_no_overlap  EXCLUDE USING gist (room_id WITH =, tsrange(start_time, end_time) WITH &&);

Best Practices

  • Use UUIDs for public-facing IDs, SERIAL/BIGSERIAL for internal
  • Always add created_at and updated_at timestamps
  • Use soft deletes (deleted_at) for important data
  • Design for eventual consistency in distributed systems
  • Document schema decisions in migration files
  • Test migrations on production-size data before deploying

來源與署名

來源:MoizIbnYousaf/ai-agent-skills位於skills/database-design提交6d95c78

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架