​

Database Schema Updates - Turbo Cache Management

​

🔧 Auto-Invalidation Setup

​

What Gets Tracked

​

🚀 Quick Commands

​

When You Update the Schema

# One command to handle cache invalidation:
pnpm schema:update

1. Regenerates the Prisma client with latest schema
2. Force rebuilds all dependent packages (@cona/core, @cona/temporal-workflows, etc.)

# Apply database migrations first
pnpm db:migrate

# Then update caches and rebuild
pnpm schema:update

​

Alternative Commands

# Just apply migrations
pnpm db:migrate

# Just regenerate Prisma client
pnpm --filter=@cona/database generate

# Force rebuild everything
pnpm turbo build --force

​

🎯 Automatic Cache Invalidation

1. Detect schema changes when you modify prisma/schema.prisma
2. Invalidate build cache for all packages that depend on @cona/database
3. Rebuild dependent packages like @cona/core, @cona/temporal-workflows, @cona/webapp

​

🧪 Testing Schema Changes

​

Before Schema Changes

# Check current migration status
pnpm --filter=@cona/database db:status

# Start local database if needed
pnpm db:start

​

After Schema Changes

# Apply changes and rebuild everything
pnpm schema:update

# Restart temporal workers if running
cd apps/temporal-workers && pnpm dev

​

⚠️ Important Notes

​

Environment Consistency

• Ensure your .env.local files point to the correct database
• Local development should use localhost:54322 (Docker)
• Production uses remote Supabase connection

​

When Turbo Cache Issues Persist

# Clear all Turbo cache
pnpm turbo build --force

# Or clear specific package cache
pnpm turbo build --filter='@cona/core...' --force

​

Temporal Workers

# Kill existing workers and restart
pkill -f "temporal-workers"
cd apps/temporal-workers && pnpm dev