[Solved] How can you ensure a migration runs only once and does not reapply in NestJS with TypeORM? — Ans: TypeORM tracks applied migrations in a special table and skips duplicates | NestJS

NestJS - Database with TypeORM

How can you ensure a migration runs only once and does not reapply in NestJS with TypeORM?

AYou need to rename migration classes after each run

BTypeORM tracks applied migrations in a special table and skips duplicates

CNestJS automatically deletes migration files after running

DYou must manually comment out migration code after running

Step-by-Step Solution

Solution:

Step 1: Understand migration tracking
TypeORM stores applied migrations in a table to avoid reapplying them.
Step 2: Eliminate manual or incorrect methods
Manual commenting, deleting files, or renaming classes are not standard or safe practices.
Final Answer:
TypeORM tracks applied migrations in a special table and skips duplicates -> Option B
Quick Check:
Migration tracking table prevents reapplication [OK]

Quick Trick: TypeORM uses a table to track applied migrations [OK]

Common Mistakes:

Master "Database with TypeORM" in NestJS

9 interactive learning modes - each teaches the same concept differently

More NestJS Quizzes

How can you ensure a migration runs only once and does not reapply in NestJS with TypeORM?