Re: EO lastModifiedTS @ validateForUpdate?
Re: EO lastModifiedTS @ validateForUpdate?
- Subject: Re: EO lastModifiedTS @ validateForUpdate?
- From: Chuck Hill <email@hidden>
- Date: Thu, 29 Nov 2007 19:43:44 -0800
On Nov 29, 2007, at 7:39 PM, David LeBer wrote:
On 29-Nov-07, at 9:01 PM, Chuck Hill wrote:
On Nov 29, 2007, at 5:53 PM, Les Vogel wrote:
I'd like to keep a last update timestamp on my entities. Would
validateForSave | validateForUpdate be a good time to modify an
attribute?
Define good. :-) That violates an EOF commandment. You risk
confusing EOF. If you are using Wonder, there is a facility in
ERXEC to have it notify your object at a safe time to do this.
Use ERXGenericRecord from Wonder.
It has willUpdate, willInsert etc that are perfect for this sort of
thing.
They are called after saveChanges but before validation so it is
safe to make changes.
Yes, that is what I was thinking of. IIRC works in concert with the EC.
Chuck
--
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden