This always makes my head hurt, but I will take a stab at it.
invalidate: tosses the snapshot, affects all editing contexts.
Forces the data to be refetched from the database.
refault: changes the eo back into a fault in the EC. Depending on
the EC's fetch timestamp and the snapshot's age, it _may_ go back to
the database for fresh data when the fault is fired. I think this
discards any uncommited changes.
refresh: pretty much the same as refault, but merges uncommitted
changes back into eo.
I have found problems with refault() and refresh() and created my own
versions that you can find in EOObject in our GVCEOFExtensions
framework. Sorry, but I don't recall the details right now.
Chuck
On Dec 8, 2006, at 2:10 PM, Dov Rosenberg wrote:
What is the difference between Invalidating an object versus
refreshing versus refaulting?
It seems that some of the methods call the others. Any commentary
on which should be used and when would be appreciated. Thanks in
advance
--
Dov Rosenberg
Conviveon/Inquira
Knowledge Management Experts
http://www.conviveon.com
http://www.inquira.com
_______________________________________________
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/chill%
40global-village.net
This email sent to [EMAIL PROTECTED]
--
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 ([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]
