Chris Duff

Hi @JonathanMagnan & @Zero3, I'm having a similar problem where **IncludeOptimized** is unexpectedly slower than **Include**. Given the history of this issue it seemed I should have a go at...

Thanks @JonathanMagnan for your quick response and your organisation's efforts on this project! However I want to ensure that the correct issue is understood. If you look at the sample...

Thanks @JonathanMagnan. Re: > A lot of code might use Expression Tree instead of reflection which would lead to performance improvement after the first compile. I think my Console application...

Thanks @JonathanMagnan for looking into this. It's a bit confusing though as **IncludeOptimized** is slower than Entity Framework even though it has a faster DB command execution time. So if...

> Is it always slower on your side? Yes. I just added some `GC.Collect()` calls to try to minimise the chance that some garbage collection was affecting results and then...

Hmmm that is interesting and I'm not sure why that'd be the case. For the closed source commercial software that I'm actually trying to use it for I'm getting measurements...

FYI I'm currently working around this by inserting the following in my `dataSource.ts` file: ``` typescript declare module "typeorm" { interface EntityManager { /** * As per normal EntityManager.query but...

> `query` is common for all drivers and not all of them support named parameters. That's why we have this limitation. Understood. But it would be nice to be able...

> > any updates? I replaced by query builder :( > > findOne with a primary key Ex: const trip = await this.tripRepository.findOne(trip.id, { select: ['id', 'corp_id', 'status'], relations: ['trips',...

FYI I'm working around this issue using the following extension method defined in my `dataSource.ts`. ``` typescript import { EntityTarget, FindOneOptions } from "typeorm"; import { EntityManager } from "typeorm/entity-manager/EntityManager";...