Automate database migrations and schema management for Wasp projects.
npx skills add https://github.com/ToonVos/empty-opensaas --skill wasp-database
Please help me install this Agent Skill. Skill: wasp-database Source: https://github.com/ToonVos/empty-opensaas/tree/main/.claude/skills/wasp-database Command: npx skills add https://github.com/ToonVos/empty-opensaas --skill wasp-database
This Skill streamlines the complex process of managing database schema changes and migrations in Wasp projects. It prevents common errors, ensures type safety, and simplifies database setup, saving developers from frustrating data sync issues.
schema.prisma, running migrations, and ensuring Wasp types are updated.status field with an enum type to your Task model in schema.prisma. This Skill will guide you through running the migration, ensuring your database is updated, and that your Wasp application's types correctly reflect the new schema.Add a new status field with an enum type to the Task model in schema.prisma. Generate and apply the migration, then restart Wasp.
High-intent search queries and answers about installing and using this skill.
Database migrations in Wasp are run using the `wasp db migrate-dev` command, which applies schema changes defined in `schema.prisma` to your PostgreSQL database. After migration completes, restart Wasp with safe-start to regenerate types and sync your application.
Edit your `schema.prisma` file to add the new field, run `wasp db migrate-dev` to generate and apply the migration, then restart Wasp. This ensures your database, migration files, and application types stay synchronized and reflect your schema changes.
Restarting Wasp after migration regenerates your application's type definitions to match the updated database schema. This prevents type mismatches and ensures your Wasp types accurately reflect changes like new enum fields or model updates.
Wasp requires PostgreSQL for advanced features like enums and background jobs managed by PgBoss. While basic schemas may work with other databases, PostgreSQL is mandatory to access Wasp's full capabilities and ensure migration reliability.
Migration files in Wasp are immutable and should never be manually edited. Modifying them breaks the migration history and causes database synchronization failures. Always use `wasp db migrate-dev` to generate migrations automatically from your schema changes.
Define enum types in your `schema.prisma` file and add enum fields to your models. Run `wasp db migrate-dev` to create the PostgreSQL enum and apply the schema change, then restart Wasp to update your application types with the new enum.
rafaelcallejaManage PostgreSQL and MongoDB schema design, queries, and administration.
proyecto26Manage PostgreSQL schemas, migrations, and queries with Prisma ORM.
tankpkgStandardize Prisma ORM production patterns for TypeScript applications.
albertdobmeyerManage SQL database tasks across SQLite, PostgreSQL, and MySQL.