On 11/23/10 10:34 PM, "Jonathan Lynch" <jonathandly...@gmail.com> wrote:
Hi Jonathan,
Idea was just simply do:
while( Db.open() is false )
keep trying open it
do some job
db.close()
At least yet in 1999 Valentina was so fast that even in this dummy way was
able handle many users ...
Of course this is the most dummy way.
You can think about it as transaction with the whole isolation level.
-------
If you want to work with true record level locks,
Then only Valentina Server is a away. (I mean for Valentina DB)
For above open/close trick, there is no sense even set record locks.
> Hi Ruslan,
>
> What is the open/close trick? Is this the idea of opening the record in
> question, loading it into the application, then closing and saving the
> record while putting some kind of marker in the record to indicate that it
> is locked - then, when the user is done with the record, the application
> again opens the record, saves the information, removes the record-locking
> notation, and closes it again?
>
> Basically doing all transactions where the user opens, does the transaction,
> and closes for every single transaction?
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
