database-prisma

Prisma manages schema evolution through two workflows: `db push` for rapid development iteration directly syncing your schema to Neon, and `migrate` for production-ready tracked history. Choose `db push` during active development and `migrate` when you need auditable change records for production deployments.

`db push` instantly applies schema changes to your Neon database without creating migration files, ideal for rapid prototyping. `migrate` generates timestamped migration files for version control and production deployments, ensuring reproducible schema history and team coordination.

Neon supports isolated database branches that work with Prisma migrations. Push schema changes to branch-specific Neon databases using `db push` for development or `migrate` for tracked changes, then validate before promoting to production to ensure schema consistency across environments.

Neon connection pooling is recommended for scalable deployments with Prisma. Configure pooled connection strings in your Prisma schema to optimize database connections, especially in serverless or high-concurrency environments, improving resource efficiency and preventing connection exhaustion.

Define Prisma models representing EFT domains—quests, traders, and progress—with required fields, proper indexes, and relation mappings. Enforce data-modeling best practices like nullable field constraints and foreign key relationships to maintain data integrity and query performance.

Run drift and publish checks before production pushes to ensure your Prisma schema matches the database state and migrations are consistent. This pre-push validation prevents schema conflicts and ensures the migration history aligns with your deployed database.