Subject | Re: [IBO] Locking rows |
---|---|
Author | Helen Borrie |
Post date | 2004-02-20T23:42:34Z |
At 09:34 AM 21/02/2004 +1000, you wrote:
the row go into Edit mode. You can catch the exception and use it to
inform the user that someone else is working on it.
OTOH, if you use the "quick transaction" approach with Read Committed and
WAIT, there will be no exception if the later transaction has a higher
transaction ID on the server. First to get the lock wins, others follow on
in "hit order".
Helen
>A question: Is there a way to tell through IBObjects if someone elseThe pessimistic lock does that. If IBO can't get the lock, it won't let
>is editing a record yet still allow the user to proceed with the edit
>using the ReadCommitted method you described above?
>
>Something like that might at least provide a warning to the operators
>that someone else may be making changes to the same record.
the row go into Edit mode. You can catch the exception and use it to
inform the user that someone else is working on it.
OTOH, if you use the "quick transaction" approach with Read Committed and
WAIT, there will be no exception if the later transaction has a higher
transaction ID on the server. First to get the lock wins, others follow on
in "hit order".
Helen