A transaction can have multiple inserts/updates/deletes. So basically what web2py is doing, is when a request comes in, it starts a new transaction with the database. Then web2py executes the models/controllers/action, which perform operations on the database. Now if web2py catches an exception, it calls a db.rollback(), and if the request finishes successfully... a db.commit()
So if web2py crashes the data is never committed, and if you raise an exception, the transaction is rolled back. -Thadeus On Tue, Dec 29, 2009 at 8:54 PM, toomim <too...@gmail.com> wrote: > ossimo, unfortunately this proposal does not solve the multi- > threading prob -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
