Re: [ZODB-Dev] tracking back to what code caused a conflicting object change

2010-07-28 Thread Marius Gedminas
A: Because it makes the logic of the discussion difficult to follow. Q: Why shouldn't I top post? A: No. Q: Should I top post? On Wed, Jul 28, 2010 at 04:19:29PM +0200, Adam GROSZER wrote: > Hello Chris, > > I guess the best solution to find places which change something would > be to hook into p

Re: [ZODB-Dev] tracking back to what code caused a conflicting object change

2010-07-28 Thread Adam GROSZER
Hello Chris, I guess the best solution to find places which change something would be to hook into persistent.Persistent._p_changed, but that might not be an easy solution, 'cause it's all C. Wednesday, July 28, 2010, 4:03:05 PM, you wrote: CW> Hi All, CW> Forwarding here as there may be more p

[ZODB-Dev] tracking back to what code caused a conflicting object change

2010-07-28 Thread Chris Withers
Hi All, Forwarding here as there may be more people with the relevant knowledge around. So, the key thing I'm trying to find is what code is changing the conflicting objects? (primarily since I'm not aware of any doing so, so it must be inadvertantly getting executed) Any ideas gratefully re