managing-dev-migrations

Use migrate dev for versioned, production-ready migrations that track schema history; use db push for rapid prototyping when you don't need migration records. Migrate dev creates timestamped migration files suitable for team collaboration, while db push syncs your schema instantly without history, ideal for throwaway experiments.

Run prisma migrate dev with the --create-only flag to generate the migration file without applying it. This lets you inspect the SQL before executing it against your database, reducing risk of unintended schema changes.

Yes. After generating a migration with migrate dev, you can edit the SQL file in your migrations folder before applying it. This is useful for adding custom logic or refining auto-generated SQL to match your exact requirements.

Both workflows operate on the same schema; switch by choosing your command based on your current need. Use db push for exploratory changes, then transition to migrate dev when ready to version migrations for team deployment or production.

Use migrate dev to create versioned migrations that team members can pull and apply consistently. This creates a shared migration history, prevents conflicts, and ensures all developers apply schema changes in the same order.

No. Db push syncs your schema without creating migration files, so it doesn't produce version-controlled records. For tracked schema evolution across environments, use migrate dev instead.