UPDATE: After more digging, the extra calls are actually being caused by change tracking (on load!), which is causing the lazy loading to look up data when tracking asks for it. This is still causing problems but means what I was wondering about earlier isn't relevant.
New question: is this happening in other peoples' uses of this or is there a way around it?
Original below:
I'm trying to use this with my EF Core project but based on the logs, it seems to be eager loading everything.
Can you confirm this still works?
I'm not using a DBContextFactory pattern in the way your example is, and I'm confused by the seemingly unused _isLazy variable in your example code. Could either of these things be a factor?
Thanks
UPDATE: After more digging, the extra calls are actually being caused by change tracking (on load!), which is causing the lazy loading to look up data when tracking asks for it. This is still causing problems but means what I was wondering about earlier isn't relevant.
New question: is this happening in other peoples' uses of this or is there a way around it?
Original below:
I'm trying to use this with my EF Core project but based on the logs, it seems to be eager loading everything.
Can you confirm this still works?
I'm not using a
DBContextFactorypattern in the way your example is, and I'm confused by the seemingly unused_isLazyvariable in your example code. Could either of these things be a factor?Thanks