On Dec 14, 2005, at 6:20 PM, Arturo Pérez wrote:
Zak Burke wrote:
[EMAIL PROTECTED] wrote on 12/13/05 3:57 PM:
In my experience, WO will update attributes persisted to the DB,
but for relations it only pulls from its cache.
AFAIK, That's only true if you don't use EOF to make the
relationship changes (think trigger or such) OR your code is wrong.
-arturo
P.S. I am willing to concede that I may be wrong about this.
Settle for kinda half wrong sometimes? :-P
I think what Zak may be thinking of is to-many relationships. For
example, take an instance that fetches an object (which I will
cleverly call A) and that object has a to-many relationship to
objects B, C and D which are also fetched (the to-many fault is
fired). If _another_ instance then deletes object B and edits object
C and adds object E to this relationship, the first instance will see
the edits to object C (if it does a refreshing fetch etc), but will
not see that B has been removed or that E has been added to the to-
many relationship. EOF caches _which_ objects are in the
relationship and that does not get refreshed when one might expect
that it would.
Chuck
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
