NoLocks // 1.9.8b10 adoption of record locks. Feedback

[Carsten Friehe]

Hi Ruslan!

>    make transactions AS SHORT AS POSSIBLE in time,
>    and select as FEW records as possible. In ideal just one.

I didn't have changed my application to the new calling format because I
don't have the time now and in the next weeks. But it looks great.

I know this from Oracle where it is done in another way. If you are calling
a normal "select xyz from abc where ..." you don't lock the records. But if
you call "select xyz from abc where ... for update of xyz" you will lock
the records for updating. If you are using Oracle*Forms, this will be done
automatically. So you write a select and this data is shown in Forms. When
the user changes a field this record is automatically locked for writing.
But if the user now goes to eat something and will come back in an hour or
so, the record is locked the whole time. so it is better not to show the
real cursor but an internal list with the selected data. And if the user
changes something make a short call with "update xyz from abc where ...".

Carsten