Maybe I'm not explaining myself correctly. I tested and it isn't working the way I need and explained.
My test was: I put a sleep(10) between step 1 and 2. On another session I changed the record in question. Checked the changed was done. Waited for the sleep to end and then step 2 wrote over the change I made on the other session. The end result is that the transaction isn't protecting (locking) the records in question, which is what I need. quinta-feira, 21 de Março de 2019 às 13:11:27 UTC, Leonel Câmara escreveu: > > The transaction is atomic, that means there's nothing happening in the > middle. Your use case is fine. Of course, that if you give the user a form, > while he's editing it, the form can be changed by others as well, in that > case you need to add your own locking or check the record for modifications > while the user was editing the form. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
