Persistent Schema again.
I'm experiencing a persistent migration state issue where Wasp is trying to apply an old schema that doesn't match my current schema.prisma file.
The Problem:
- My schema.prisma has a simple BudgetItem model
- But wasp db migrate-dev keeps trying to create phantom tables (Budget, BudgetCategory, Guest, Vendor) that don't exist in my schema
- This causes the Prisma client to not generate properly, so my budget operations aren't available
- Getting TypeScript errors like: Module '"wasp/client/operations"' has no exported member 'getBudget'
What I've tried:
1. Dropped the entire database and recreated it
2. Deleted all migration files in /migrations
3. Removed .wasp directory
4. Cleared Prisma client cache in node_modules/.prisma
5. Reset the _prisma_migrations table
Current state:
- Database is fresh (empty)
- No migration files exist
- But Wasp still tries to apply the wrong schema during wasp db migrate-dev
How can I completely reset Wasp's migration state so it uses my current schema.prisma instead of some cached version? Is there another location where Wasp stores migration state that I need to clear?
The Problem:
- My schema.prisma has a simple BudgetItem model
- But wasp db migrate-dev keeps trying to create phantom tables (Budget, BudgetCategory, Guest, Vendor) that don't exist in my schema
- This causes the Prisma client to not generate properly, so my budget operations aren't available
- Getting TypeScript errors like: Module '"wasp/client/operations"' has no exported member 'getBudget'
What I've tried:
1. Dropped the entire database and recreated it
2. Deleted all migration files in /migrations
3. Removed .wasp directory
4. Cleared Prisma client cache in node_modules/.prisma
5. Reset the _prisma_migrations table
Current state:
- Database is fresh (empty)
- No migration files exist
- But Wasp still tries to apply the wrong schema during wasp db migrate-dev
How can I completely reset Wasp's migration state so it uses my current schema.prisma instead of some cached version? Is there another location where Wasp stores migration state that I need to clear?
