#Migrations not triggering upon changing entity schema

3 messages · Page 1 of 1 (latest)

swift arch
#

Hello. I made some changes to my entity file in a NestJS application, and when running the following command: npx mikro-orm migration:create it said there are no available migrations that everything is up to date. If I change my entity's schema, what is the "correct" way to generate a migration?

safe ether
#
  1. How does this ORM detect migrations that are not run? Some ORMs have a state field with up or down values.
  2. Are you sure that you are pointing at the correct migration directory?
narrow monolith
#

So are you using migrations or just schema?