mikro-orm migration:fresh --drop-db runs migrations against wrong db

[petergledhillinclusive]

Describe the bug

When the migration:fresh command is run with drop-db, the database is dropped correctly but then the migrations are run against the 'postgres' db rather that the db specified in the config.

Reproduction

When generate.dropSchema is executed with 'dropDb: true' Mikro connects to the 'postgres' db to run the drop command command but then never switches back to the user provided dbName.

private static async handleFreshCommand(args: ArgumentsCamelCase<Opts>, migrator: IMigrator, orm: MikroORM) {
   console.log(orm.config.get('dbName')); // dbName is correct
   await generator.dropSchema({ dropMigrationsTable: true, dropDb: args.dropDb });
   console.log(orm.config.get('dbName')); // dbName is now 'postgres' - migrations run against 'postgres' db rather than the original db

What driver are you using?

@mikro-orm/postgresql

MikroORM version

6.2.6

Node.js version

20.9.0

Operating system

macOS

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
• The provided reproduction is a minimal reproducible example of the bug.