[555] in Tooltime
Re: Records locking
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue Nov 18 13:39:47 1997
In-Reply-To: <v03020908ff0b41c3b745@[18.81.0.146]>
Date: Tue, 18 Nov 1997 13:44:10 -0500
To: Barbara Goguen <goguen@MIT.EDU>, tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Wow, I am glad we found this one.
Ah, yes, I remember this discussion
The help desk staff said that they wanted the log to stay on the screen
after saving the record. For this to happen, the record needs to stay
locked, yet it is saved to the database.
Sounds like the New button should issue the same logic as when backfilling
a record from the result set, that is, issue an update to clear all locks
for the consultant. Probably a SQL such as "update mit_logs set
mit_record_lock = 'N' where mit_record_lock_user = $user.
If everyone agrees, I would like to get this change in production this
week, which means we need time to test the change on the test database
before moving to production.
David, do you have time to take a look at this?
What does everyone say?
..Steve
At 1:28 PM -0500 11/18/97, Barbara Goguen wrote:
>One of the students this morning was having trouble with records locking.
>I watched him as he worked. He was clicking New to create new logs, then
>adding in info for a log, clicking Save to save the updates. Then he would
>try to click New again to start another log and it would give him an error
>that he needed to save changes. He would try to save changes again, and it
>wouldn't let him. Looking under view locks the record would be locked.
>
>When he instead did New to start a new record, made changes then clicked
>Save, then clicked Clear before clicking New again, it seemed to leave the
>records unlocked. Is this how it is designed to work, that you have to
>click Clear before clicking New again?
