Roundup Tracker - Issues


Author schlatterbeck
Recipients ThomasAH, ber, ezio.melotti, rouilj, schlatterbeck
Date 2013-01-09.08:11:59
Message-id <>
In-reply-to <>
On Mon, Jan 07, 2013 at 08:46:19PM +0000, Bernhard Reiter wrote:
> When running with postgresql, the problem is that the history is not set
> to the right value. Yes, I would expect a locking mechanism in the database
> to prevent this, a transaction would be cool. However it does not prevent it.
> Maybe that is the result of line 2996 of
>    oldvalues = copy.deepcopy(self.db.getnode(self.classname, itemid))

Yes, if this happens outside the transaction this could be the reason
that all the transactions get the same history. If it happens inside the
transaction postgres should note that the issue is *read* and see a

I think I'll have to look into this more closely...

Date User Action Args
2013-01-09 08:12:00schlatterbecksetrecipients: + schlatterbeck, ber, rouilj, ThomasAH, ezio.melotti
2013-01-09 08:12:00schlatterbecklinkissue2550731 messages
2013-01-09 08:11:59schlatterbeckcreate