tl;dr you can't . You ABSOLUTELY can't survive a transaction in different processes. If you need to control concurrency, implement your own "lock" in the app (i.e. using a "light" record in a table).
On Friday, September 30, 2016 at 7:30:30 PM UTC+2, Pierre wrote: > > Hi, > > it's late and the race (condition) goes on............. > trying to define a concurrency control strategy, my idea is (1) to have > global defaults transaction mode parameters in the posgresql. config file > and (2) to depart from these when action/transaction is read-only. Howewer > it's not clear how to achieve (2) since I don't fully understand how w2p > manages transactions. The way to do that in postgresql reference doc is to > issue a BEGIN or START TRANSACTION sql command followed by the transaction > mode (isolation level, read/write mode,deferrable mode). There's another > possiblity that consists in using current transaction uid (sql command: > SET TRANSACTION SNAPSHOT). how do I go with this ? how do I get current > transaction uid. Where do I have to place the sql command to set individual > transaction mode parameters? > -- 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.
