Yes, I believe so. Basically that ObjectsChangedInStore goes to any
living EC so they know to update their local caches. If you have
inserted objects in your EC (into to-many's), it would need to merge
changes with the new ones in the snapshot cache. For a to-many
change, I believe you just send an UpdatedKey in the notification's
userInfo with the source global id.
ms
On May 15, 2007, at 5:53 PM, Andrew Lindesay wrote:
Hello Mike;
You say below you're calling "forgetSnapshotForGlobalID(...)".
Under what circumstances? That would likely cause this ... If you
have living EO's, you can't just forget their snapshots without
filling them back in or I would expect you'd get this exact
situation (i.e. an EO in an EC that has a {} snapshot). OSC-
locking, btw, is sufficient. Mucking with the snapshots behind the
scenes requires that you post an ObjectsChangedInStoreNotification
so the EC's all pickup the change.
If I were also modifying a "to-many" snapshot using...
EODatabase.recordSnapshotForSourceGlobalID(...)
I imagine that I would also need to send off a notfication -- is
that the case?
cheers.
___
Andrew Lindesay
technology : www.lindesay.co.nz
business : www.silvereye.co.nz
_______________________________________________
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]
