Re: Best Way To Determine If An EO Has Ever Been Saved
Re: Best Way To Determine If An EO Has Ever Been Saved
- Subject: Re: Best Way To Determine If An EO Has Ever Been Saved
- From: Stephane Guyot <email@hidden>
- Date: Tue, 17 May 2005 19:46:41 +0200
Hunter,
Perhaps nested editingContext may help you in your situation.
Another idea is insertedObjects(), updatedObjects(), deletedObjects()
... API on EOEditingContext.
HTH,
Stephane
Le 17 mai 05, à 19:25, Hunter Hillegas a écrit :
What is the best way to determine if an EO has ever been saved?
I have a process that creates a new EO and inserts it into an EC.
I would like to be able to tell if the EO has ever been
saved/committed to the DB.
I only need to differentiate between saved/unsaved, not if the EO has
later been changed but those changes haven't been saved.
EOEditingContext.hasChanges() is too general for me in this case. I
only want to know about the initial commit.
Is there an easy way to do that?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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