Martin Adámek
Martin Adámek
> So these are not the same? Nope, the first one is not a valid query, you are mixing populate with where condition, those are separate things. What I am...
> Actually I don't think I am - findAll(), according to this, accepts either a Populate object or a FindOptions object as its first argument, and FindOptions allows a populate...
> The intended outcome was that all authors would be loaded, and for each of them, all their books with a title matching the specified condition - so findAll authors,...
Less clunky workaround is via array destructing: ```ts const [card] = await em.find(...); ``` But I dont mind having offset there, feel free to send a PR.
> Since using object embedded properties is allowed on mongo/mysql/postgresql only Why do you think so? I believe it should work just fine with sqlite too (although querying by embedded...
Can somebody create a "repro" that would demonstrate what behaviour and why would you want to change?
I was asking for a reproduction of the problem this is supposed to be solving, not another one line example of how it should work.
Not yet supported.
It should go to the core package, it should be driver independent (but end users will have the correct EM flavour, with `createQueryBuilder` available for SQL drivers). I am not...
> I think is needed to hydrate the properties? i would check the implementation on typeorm. Yeah well we need a decorator, my point was that `@Property()` could be enough....