No changes in database schema were found – cannot generate a migration. to create a new empty migration use “typeorm migration:create” command

When you see the message “no changes in database schema were found – cannot generate a migration. to create a new empty migration use ‘typeorm migration:create’ command,” it means that the TypeORM migration system detected that there are no changes in the entities or the database schema, so it cannot generate a migration automatically.

TypeORM compares the current state of your entities with the previous state stored in its metadata to determine if there were any changes that require a migration. If no changes are found, it cannot create a migration file since there is no difference to apply.

However, if you still want to create a new migration even without any changes, you can use the ‘typeorm migration:create’ command. This command will create an empty migration file that you can later use to manually write migration operations if needed.

Here is an example of how to use the ‘typeorm migration:create’ command in the terminal to create a new empty migration:

    
      $ npx typeorm migration:create -n EmptyMigration
    
  

In this example, the ‘-n’ option specifies the name of the migration. Replace ‘EmptyMigration’ with the desired name for your migration file.

After running the command, TypeORM will generate a new empty migration file in the configured migration directory. You can then open this file and manually write migration operations if needed, such as creating or modifying database tables, indexes, or constraints.

Remember, creating an empty migration file without any changes is usually not necessary. Migrations are meant to synchronize the database schema with the entity definitions automatically. Only create a new migration if you have made changes to your entities or want to perform manual database schema modifications.