You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When processing a select, depending on a resolver, child objects may or may not be stored in ResourceEntity. The default Cayenne strategy ("relatedViaQueryWithParentExp") actually stores them, while a few others like "relatedViaParentPrefetch" do not. This causes issues like #626.
We must change the resolver lifecycle, to unconditionally store children in their respective ResourceEntities, regardless of the how they were resolved. This will make the rest of the pipeline more sane, as well as simplify RelatedDataResolver itself.
The text was updated successfully, but these errors were encountered:
andrus
changed the title
Always install related objects in ResourceEntity
Always store child result objects in ResourceEntity
Apr 9, 2023
andrus
changed the title
Always store child result objects in ResourceEntity
Always provide access to child data at the RelatedResourceEntity level
Apr 9, 2023
When processing a select, depending on a resolver, child objects may or may not be stored in ResourceEntity. The default Cayenne strategy ("relatedViaQueryWithParentExp") actually stores them, while a few others like "relatedViaParentPrefetch" do not. This causes issues like #626.
We must change the resolver lifecycle, to unconditionally store children in their respective ResourceEntities, regardless of the how they were resolved. This will make the rest of the pipeline more sane, as well as simplify
RelatedDataResolver
itself.The text was updated successfully, but these errors were encountered: