NoLocks // 1.9.8b10 adoption of record locks. Feedback

[Ruslan Zasukhin]

on 7/5/03 11:07, erne at ernestogiannotta at tiscalinet.it wrote:

> some dumb questions:
> what's the price of notify cursors of changes?
> huge overhead? system clogging?

DBMS server will need do extra work to check what cursors must be notified,
And notify them
 
Again, this is not good way how transactions work.
Do not worry, you will become used.
I am self yet not used to this tricks :-)


> as things stand now
> what's the way to know our local data are no more up-to-date?
> 
> i = SqlExecute("Update t set f = 'hi' Where recid = 1")
> will fail if recid 1 is locked somewhere?
> i.e. i = 0 and db.Error = CannotSetlocks
> 
> and what if
> i = SqlExecute("Update t set f = 'hi' Where f = 'ho'")
> and we have 10 records with f = 'ho'
> will fail if just 1 of the satisfying records is locked somewhere?

Yes it fail.


-- 
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
-------------------------------------------------------------