Because EOF doesn't know if your relationship can be completely
satisfied by objects in memory, it must go to the database. As Guido
mentioned, you can do a prefetch (or batch fault) the relationship to
improve performance.
Also, when it goes to the DB, if the object is already in memory and
is not older than the timestamp you set on your EC, it will not be
loaded from the table again - EOF will just link the existing object in.
Ken
On Aug 24, 2006, at 7:15 PM, Marcos Trejo Munguia wrote:
Hi List,
I have a doubt related to object caching, suppose you have the next
relationship A<->>B, if you fetch objects of A, then objects of B,
it isn't supposed that when you access objects of B through objects
of A this objects of B are already cached in memory and there's no
need to do a trip to the db to bring them? Because I,m debugging
the SQL that EOF generates and this is not happening, another query
is performed to bring those objects B related to object A. It isn't
enough to fetch the objects that you need to get them cached in
memory?
Cheers
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/lists%
40anderhome.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
