Re: refreshing and relationships
Re: refreshing and relationships
- Subject: Re: refreshing and relationships
- From: Tom Woteki <email@hidden>
- Date: Sun, 15 Jan 2006 17:19:38 -0500
| I've come to the conclusion that you are correct as below. Several other tips I've received also seem to assume an in memory array. I've been trying to avoid that, thinking the object graph would save me and wondering why it is isn't. Your explanation is the one that fits the behavior I'm observing.
Thanks for the help Xavier. Tom
On Jan 15, 2006, at 4:44 PM, Dev WO wrote: As far as I understand it, the relationship doesn't display the expected array because the relationship comes from the datastore and not the editing context so even if you remove in the editing context, it's not "updated" back to the relationship because it's not actually saved. The refreshing "action's" like refreshObject only "force" a refresh from the datastore, so as it hasn't been saved, you'll get the original array and not the edited one.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden