Stuart Clarke <[EMAIL PROTECTED]> writes: > *** The test-and-set operation isn't atomic though, is it? Which still > leaves the door (slightly) open for simultaneous executions.
It depends how you're doing it. I'd try locking the table for update, updating it and then starting the process. If you were doing a "SELECT/UPDATE" without locking then it would be easier to have problems. > Might be the best possible solution, however. I believe so. Sharing something through NFS is unreliable as well... I believe that memcached also has the non-atomic behavior. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
