Thanks Jeremy,
but could you speak more slowly please? ;-)
Which debug log are you refering to? There is nothing in the stupid log,
and "Big M" logging does also not give me any indication of conflicts or
oids. Do I have to run everything inside pdb?
I also do not seem to figure out where th
> "SHH" == Stefan H Holek <[EMAIL PROTECTED]> writes:
SHH> Hi All! I am experiencing a lot of 'ZODB conflict error at
SHH> ...' that I can reliably reproduce by hitting my browser's
SHH> Refresh button at a high rate. The bad news is that the
SHH> conflicts happen on pages that are n
Yes, but AFAIK read conflicts mean that something has changed during a
read. I do not expect this to happen either...
Stefan
--On Freitag, 11. Oktober 2002 07:54 -0400 Jens Vagelpohl <[EMAIL PROTECTED]>
wrote:
conflict errors do not imply conflicting writes by definition. there is a
thing cal
conflict errors do not imply conflicting writes by definition. there is
a thing called "read conflict", which is probably what happens to you.
jens
On Friday, Oct 11, 2002, at 07:47 US/Eastern, Stefan H. Holek wrote:
Hi All!
I am experiencing a lot of 'ZODB conflict error at ...' that I can
Hi All!
I am experiencing a lot of 'ZODB conflict error at ...' that I can reliably
reproduce by hitting my browser's Refresh button at a high rate. The bad
news is that the conflicts happen on pages that are not supposed to change
anything in the ZODB but only display results of some SQL queri
