Re: Checking for uncommited transactions

Well, let me explain this stuff again because I cannot understand whether you are suggesting a sort of "batch" update from the client to the server once the user has "saved" the changes locally or you are assuming that the client is working in autocommit mode. In this case autocommit would be turned off.

The user changes a value in a form (loaded with a SELECT FOR UPDATE, just to be safe).
The form actually updates the record because it invokes a stored procedure that, in turn, UPDATEs a record in a table. No one can see any change because the user didn't commit yet.
He exits from this form and enters a new one, changes another value and exits from the form.
Again, the form updates the record by invoking another stored procedure updating another table.
No commit until now, so, if the user "saves" (that is he issues a commit), the changes will take place in both tables and become visible to others. If he "undoes" (that is rolls back the previous transactions), the changes are discarded and the locks on the two tables are gone.

What's wrong with this scenario?

Bye,
Flavio Received on Thu Mar 06 2003 - 11:36:22 CST