Eager loading by default possible ?

Hello list,

With a query you can use the alsoFetch:  method to "eager load" related objects. Is it possible to specify a mapping so that Glorp does this by default?

My Model is something like this:

Class A ----(*)--> Class B ----(1)--> Class C

Class A has a collection of B instances and each B instance refers to exactly one C instance. What I would like to have is that when Glorp loads the the collection of B instances for an A instance it also loads the C instances using a join query.

Cheers,

Jan.

--
You received this message because you are subscribed to the Google Groups "glorp-group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/212f6892-ae48-479b-b411-b149494208d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jan,

please be very sure you ALWAYS want these dependent objects loaded. We've used this just to find out there are situations in our Application where this is not desired.. ;-)

I have a related question I have been wondering about for a while:

What is the exact difference between shouldProxy: false and alsoFetch:?

All I've found out so far is that shouldProxy doesn't work as expected, but I haven't found out what exactly to expect ;-)))

Joachim

Am Donnerstag, 6. Juni 2019 20:37:08 UTC+2 schrieb Jan van de Sandt:

Yes, I found an example and now it works. 

The mappings looks like this:

mapping := (aDescriptor newMapping: ToManyMapping)

attributeName: #b;

referenceClass: B;

join: (Join

from: (table fieldNamed: 'ID')

to: (bTable fieldNamed: 'A_ID')).

mapping query alsoFetch: [ :each | each c ].

Thank you!

On Thursday, June 6, 2019 at 7:02:34 PM UTC+2, alan.knight wrote:

Yes, it's definitely possible. Look for sends of alsoFetch: inside descriptors in the tests.

On Thu, 6 Jun 2019 at 09:31, Jan van de Sandt <[hidden email]> wrote:

Hello list,

With a query you can use the alsoFetch:  method to "eager load" related objects. Is it possible to specify a mapping so that Glorp does this by default?

My Model is something like this:

Class A ----(*)--> Class B ----(1)--> Class C

Class A has a collection of B instances and each B instance refers to exactly one C instance. What I would like to have is that when Glorp loads the the collection of B instances for an A instance it also loads the C instances using a join query.

Cheers,

Jan.

--
You received this message because you are subscribed to the Google Groups "glorp-group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/212f6892-ae48-479b-b411-b149494208d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "glorp-group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/6a324a5a-5131-448f-ba80-722d51dfdb34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.