On 31/08/12 15:40 -0700, Tristian Paul wrote: > On Monday, August 20, 2012 6:43:26 PM UTC-7, Tristian Paul wrote: > > > > Hi all, I sometimes get a weird message with no stack trace when I try to > > save some model records, It says: > > "Concurrency Exception", the message box is the small one with a red minus > > icon I haven't been able to > > trace the root cause as that is all the information that it shows, after > > it appears the model is not saved and > > where or what could originate that message a red label containing "invalid > > form". I don't get te message with > > all the models just with some like the 'res.group' and a one that I > > created. > > > > Any help is really appreciated. > > > > > Looking at the source code of modelsql.py, in the write method the > ConcurrencyException is thrown when the Transaction().timestamp contains > values > and a model id is returned from a query that casts the write_date or > create_date to a decimal, I assume that it checks if the record and related > records have > been modified by another user while we performed the edits, my question is > how exactly is the Transaction().timestamp field populated,
It is done by the client and filled with the timestamp of the read. > I logged it and it contains id and model names as well as a timestamp > value, however no matter how much I wait, the Transaction's timestamp > property doesn't > get cleared or reset, which I believe is what blocks the edit. What could > be causing said behavior. Could you give a scenario to reproduce the error? -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpDNidCSxDGD.pgp
Description: PGP signature
