Martin Adámek

You could try this as a workaround: ```ts qb.select('*') .leftJoin('a.books', 'b', { 'b.foo': { $ne: '1', }, }); ```

Hmm looks like this is not really supported by knex, you cant have a generic `not` condition in the on clause, so this will require quite a redo of how...

I will try to refactor the QB to be less dependent on knex here, I want to gradually move away from it (will keep it as a query runner, but...

Damn this was challenging, but I finally have the tests green.

Thanks for the poke, I know this is missing. I would suggest you take a look at the joist orm docs, as this concept is mostly implemented based on that:...

Optional properties are a different story, its unrelated to the `Loaded` type - `Loaded` type [directly intersects the `T`](https://github.com/mikro-orm/mikro-orm/blob/master/packages/core/src/typings.ts#L664), in other words its always assignable to `T`. This is already...

Yeah agreed its a common question, got it on stack overflow very early after 5.0 release :] just checked, and it was less than 24 hours :D https://stackoverflow.com/questions/71013801/optionalprops-in-mikro-orm I am...

It wont change the type of your entity, it will return it. You would have to have a new variable: ```ts const [loadedEntity] = await this.getEm().populate(myEntity, ['other']); // loadedEntity ===...

Just destruct, this is correct behaviour in v5, it always returns array as it was giving hard times to TS inference otherwise: ``` const [loadedEntity] = await this.getEm().populate(myEntity, ['other']);

I think I would rather have something like `em.ensure(entity)` or `em.upsert(entity)`, both would automatically run the insert query if match is not found - depends on the driver support, but...