NoLocks // 1.9.8b10 adoption of record locks. Feedback

[Ruslan Zasukhin]

on 7/4/03 18:20, erne at ernestogiannotta at tiscalinet.it wrote:

>> Thinking about how Filemaker Pro handles this, (if I'm not mistaken),
>> you can always read any record and it will show you the last modified
>> state. (It will automatically notify other cursors of changes.)

I have explain that this is bad idea to notify all cursors on changes.
Only DB Server with small number of users can allow to self do this.

>> It will
>> simply not allow two users to modify (be in Write mode on) the same
>> record. That is a much more livable process. Is this what Valentina
>> does, or can we have it do that?
> 
> maybe noLocks should behave this way
> i.e. same as readonly but let others lock its records for change
> as opposed to ReadOnly lock which ensures data are not changed behind your
> back while you are browsing them
> 
> I still think that this approach and the possibility to manual lock/release
> cursors even on a single record basis would permit much more flexible
> designs (of course leaving to those who want/need to be more strict the use
> of the current approach)

Please note, this is alpha implementation.
It give us now safe multi-user way.

For 2.0 release we may have little other behavior.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------