Bjorn Stabell wrote:
In any case, is there no way to find out more detailed information about
why a conflict happened? There must be some oids somewhere?
I don't know of a way. In a conflict, the transaction gets aborted, so
the only data left is the log entry.
Shane
Bjorn Stabell wrote at 2003-6-3 11:08 +0800:
Except for SARS, another problem that's been plagueing us for months are
seemingly random Conflict Errors. We see about 10 every day on our Zope
2.6.1, and they can happen on any page. In most cases they are not
related to pages that actually
Bjorn Stabell wrote at 2003-6-3 11:04 +0800:
During packing, we're seing errors such as the ones attached below. Can
someone give a description how to track down which objects have these
broken references? Such help would be much appreciated...
Maybe the fsrefs.py script.
A short time
To anyone not following the Problem committing zope 'version' objects
thread on [EMAIL PROTECTED]: It's been proposed that Versions should be
at least stamped in the ZMI with big warnings, or possibly disabled
altogether. Numerous users have been bit by the fact that versions
basically do not
To anyone not following the Problem committing zope 'version' objects
thread on [EMAIL PROTECTED]: It's been proposed that Versions should be
at least stamped in the ZMI with big warnings, or possibly disabled
altogether. Numerous users have been bit by the fact that versions
basically do
IMO versions do nothing except complexify the code. I believe it's an
official Zope Corp position to discourage them for new projects. Yet
Jeremy Hylton seems to think that they are somehow useful and has
carefully preserved them in ZODB 4 (== Zope 3). If it were up to me,
they would have
Guido van Rossum wrote
IMO versions do nothing except complexify the code. I believe it's an
official Zope Corp position to discourage them for new projects. Yet
Jeremy Hylton seems to think that they are somehow useful and has
carefully preserved them in ZODB 4 (== Zope 3). If it were up
Dieter Maurer wrote:
The attached patch to Zope/App/startup.py provides this
additional information.
Where's the patch?
cheers,
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
Paul Winkler wrote:
Comments?
They really should die. They cause nothing but pain and suffering.
Could we get at least some warnings in the ZMI before
2.6.2 final?
I do hope so. I'd also like to see them becoming an explicit configuration
option in 2.7 and not appear in any UI's unless they
Chris Withers wrote:
Dieter Maurer wrote:
The attached patch to Zope/App/startup.py provides this
additional information.
Where's the patch?
http://marc.theaimsgroup.com/?l=zope-devm=105466926610469q=p3
--
Jamie Heilman http://audible.transient.net/~jamie/
I was in
Paul Winkler wrote:
To anyone not following the Problem committing zope 'version' objects
thread on [EMAIL PROTECTED]: It's been proposed that Versions should be
at least stamped in the ZMI with big warnings, or possibly disabled
altogether. Numerous users have been bit by the fact that
Paul Winkler wrote:
To anyone not following the Problem committing zope 'version' objects
thread on [EMAIL PROTECTED]: It's been proposed that Versions should be
at least stamped in the ZMI with big warnings, or possibly disabled
altogether. Numerous users have been bit by the fact that
Perhaps Jeremy could run through his reasons for wanting them to
stay around again?
That's not necessary. They could stay in ZODB (certainly cutting them
out of ZODB3 now would be more work than leaving them in) but be
disabled in ZMI.
--Guido van Rossum (home page:
13 matches
Mail list logo
