Files
neta/docs/database
Poyraz Avsever 35dd88b5af feat: implement project management features with cover images and planning sections
- Add ProjectsClient component for managing projects with a grid and list view.
- Introduce project cover image functionality and related fields in the database.
- Create a new table for project planning sections with RLS policies for user access.
- Update global styles for scrollbar customization.
- Enhance Next.js configuration for server actions with increased body size limit.
- Document new database migration for project planning assets.
2026-06-04 15:45:51 +03:00
..

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

  1. Every SQL change must have a stable order number.
  2. Every SQL file must be listed in query-order.md.
  3. Every executed query must be recorded in query-log.md.
  4. Every meaningful schema addition must have a short documentation file under this directory.
  5. 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