Database Change Process
This directory records every database change that should be run against Supabase/PostgreSQL.
The project currently starts with supabase/schema.sql as the first database query file. Future database changes must be added as separate SQL files and registered here before they are run.
Rules
- Every SQL change must have a stable order number.
- Every SQL file must be listed in
query-order.md. - Every executed query must be recorded in
query-log.md. - Every meaningful schema addition must have a short documentation file under this directory.
- Do not edit an already executed SQL file silently. Add a new ordered SQL file instead.
Current Files
supabase/schema.sql: Initial legacy schema. It creates the current auth/profile, journal, task, chat, and avatar storage structure.supabase/migrations/0002_add_freelancer_os_core_tables.sql: Freelancer OS MVP core schema.supabase/seeds/0001_demo_freelancer_os_data.sql: Optional local/demo data for the MVP schema.docs/database/0001-initial-schema.md: Explanation for the initial schema.docs/database/0002-freelancer-os-core-tables.md: Explanation for the MVP schema migration.docs/database/seed-0001-demo-freelancer-os-data.md: Explanation for the demo seed file.docs/database/query-order.md: Canonical order of SQL files.docs/database/query-log.md: Manual execution log for SQL files that were run against an environment.
Next Migration Naming
Use this pattern for future SQL files:
supabase/migrations/0002_short_description.sql
Example:
supabase/migrations/0002_add_freelancer_os_core_tables.sql
Use this pattern for future seed files:
supabase/seeds/0002_short_description.sql