All finders are setIncludesSubentities:YES #112

Closed
appsperhaps opened this Issue Dec 15, 2011 · 5 comments

4 participants

@appsperhaps

Hi again,

I don't see any references to setIncludesSubentities in the MR codebase, so by default all entities are retrieved with their subentities attached. As I understand it, this could be a performance drawback if there are many child entities?

Is this something that's being worked on? I could help when I get the time.

Thanks!
Jeff

@magicalpanda
@appsperhaps

Thanks for that - I almost exclusively use setIncludesSubentities:NO all the time, and lazily load child entities. One of my entities could have upwards to 500 child entities you see.

Anyway thanks for that feedback, I might change my local MR to set the above, and think of a way to work it back into the MR codebase if you're open to it.

Thanks!
Jeff

@magicalpanda
@paulthorsteinson

@appsperhaps Did you ever work that in to the codebase? I would be interested in that as well. In my project for example I have a object and then a subclass that is just a historical snapshot with the same columns plus one (original object id) so subclassing makes sense. But when deleting parent class we dont want to clear history. So it would be nice to have some config option. I may add and do a pull request if I have time.

@tonyarnold tonyarnold closed this Aug 19, 2013
@tonyarnold

Closing due to lack of updates — be sure to re-open if there’s anything outstanding you’d like addressed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment