What is the best way to handle database migrations safely using PrismaORM in a TypeScript project so that migrating production data does not accidentally drop our household task manager tables?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What is the best way to handle database migrations safely using PrismaORM in a TypeScript project so that migrating production data does not accidentally drop our household task manager tables?
1 real search · 1 real-search pass
Prisma ORM official documentation production migration deploy migrate dev reset db push expand contract migration safetyGoogle ↗
OBSERVEDInstruction
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
Prisma ORM official documentation production migration deploy migrate dev reset db push expand contract migration safety Google ↗
- Development and production (Prisma ORM v6) · prisma.io
- prisma migrate deploy | Apply Migrations to Production · docs.prisma.io
- How to migrate data with Prisma ORM using the expand and contract pattern · prisma.io
- How to migrate data with Prisma ORM using the expand and contract pattern · docs.prisma.io
- Deploying database changes with Prisma Migrate (Prisma ORM v6) · prisma.sh
- How migrations work in Prisma ORM · prisma.io
- Development and production workflows · prisma.io
- Baselining existing databases · prisma.io
- Migration troubleshooting · prisma.io