Yes, that's possible, but then I wouldn't know if I need to update the whole database (if something was deleted) or just one row if it was updated and it could make a difference (time-wise).
I was thinking of trying out the approach of creating a special table, for example: network(busy,action,name) and then before a transaction write to that table the values and after a transaction clear those values. Before writing to this table though, I'd check for values that are already there and if there're any values, then it's busy and that machine should wait, otherwise just continue. Does that sound reasonable? Are there any potential flaws in my logic here? Thank you! Dennis ----- Original Message ----- From: "Tito Ciuro" <[EMAIL PROTECTED]> To: "Dennis Volodomanov" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 29, 2003 9:49 PM Subject: Re: [sqlite] Checking the busy state Hello Dennis, On miércoles, octu 29, 2003, at 09:16 Europe/Paris, Dennis Volodomanov wrote: > That issue is, if I query a row before I want to change it, and I get > some > values, and reading from a database is allowed by all, even if the > database > is locked for writing, then how will I know that the database was > changed? One way is to keep track of the db's timestamp. You can check the value at key points and determine whether it has changed or not, then re-query as needed. -- Tito --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
