Re: EOModeler and more
Re: EOModeler and more
- Subject: Re: EOModeler and more
- From: james cicenia <email@hidden>
- Date: Mon, 12 Jan 2004 14:36:44 -0600
The following has me confused.
Should I not use fetch specs? In other words, while all my objects are
looking good and all my relationships clean are
clean should I use fetch specs or should I just get all the objects
through the relationship and then filter them programatically?
Or, is there a secret when creating relationships that will select a
subset. My Portfolio object has a one to many
relationship to requests, however I just want to show only open
requests as an example.
I of course want to take advantage of caching. Also, only after
clicking on a request would I need to worry about updates.
-James
On Jan 12, 2004, at 2:16 PM, Chuck Hill wrote:
Arturo Pirez wrote:
BTW, no fetch spec result is cached. That will always go to the
database. I'm not certain if
the resultant objects are cached or not. So I try to write things
such that I only go through
relationships. Those are cached and offer amazing performance. But
it's not always possible.
If the fetch is marked as refreshing refetched objects then the newly
fetched rows will update the cache. Otherwise only the PK (and
Entity, restricting value) is used to identify the snapshots already
cached.
Chuck
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.