Martin Adámek

> to reuse the same table for different purposes. That is called single table inheritance: https://mikro-orm.io/docs/inheritance-mapping#single-table-inheritance Or maybe you have a [table-per-type inheritance](https://github.com/mikro-orm/mikro-orm/issues/1575)? That's unfortunately not supported.

Any reason why #12179 is not yet merged? This problem breaks the request context middleware for MikroORM users when combined with `setGlobalPrefix()`, I can confirm the same observations as @ealmansi....

It would be great if you could reopen and revisit this, it's clearly not fixed ([and it's not just me who confirms this](https://github.com/nestjs/nest/pull/13337#issuecomment-2099150093)), at least not the part that the...

How was it breaking? I recall there were no tests broken by it, so how can someone tell if it's breaking or not without it?

I don't know what that means really, I hope someone who actually uses nest and knows the internals can proceed with this, I am unfortunately not the right person. I...

Not entirely sure how this works, I remember `tap` was just a side effect without waiting, if so, I would rather wait for the flush to finish before you resolve...

This could be a bit smarter, I'd say it should be a new [logger namespace](https://github.com/mikro-orm/mikro-orm/blob/a60d6042c19f63e162015940da56faa76bd659be/packages/core/src/logging/Logger.ts#L34), and queries that will be over the threshold should be printed as warnings (so in...

Maybe @SpencerKaiser will have some opinions on this, as he did quite a lot of improvements in the logging in v6.

I don't think we need `--fake`, that feels weird to me. But we can have a command to log/unlog a single migration by name, that feels quite handy and is...

No, log and unlog are umzug names to add/remove lines from the migrations table, it has nothing to do with logging as in printing stuff to console.