Re: Automatic indexing solution
Re: Automatic indexing solution
- Subject: Re: Automatic indexing solution
- From: Florijan Stamenkovic <email@hidden>
- Date: Tue, 19 Jul 2005 14:43:01 +0200
On Jul 19, 2005, at 13:07, Florijan Stamenkovic wrote:
Add an isSaving boolean to Application. Upon user invoking
saveChanges() in my component first checking if the app is unlocked,
then locking the "saving process" on application level through
(setIsSaving(true)), fetching the last record, update new records with
booking numbers, save the to the database, unlock the app for saving,
display the records to the user so they can do what they want with the
booking numbers of those records. Since all is happening in one
method, I could make a try / catch / finally block to make sure that
the boolean for allowing saving does not stay set to false if an
exception is thrown.
Darn, then it is still possible to have another instance making a
request for the last booking record in between the first instance
getting the last number and saving it's new records. How about
declaring the boolean in Application as static???
Flor
_______________________________________________
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