On Thursday, October 23, 2014 12:52:33 PM UTC-4, Leonel Câmara wrote: > > Doesn't the database take care of that? I mean isn't db session handling > inside a transaction anyway? >
Yes, but that doesn't help across requests (e.g., request A reads session > request B reads session > request A updates session > request B overwrites request A's update). The session table in the db does include a "locked" field, but as far as I can tell, it is not actually used. Another option would be to do a select-for-update, which would result in the db locking the record until the transaction completes (though in the case of SQLite, I think the whole db gets locked). Anthony -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
