[Florent Guillaume]
> Plagiarism! ;)
> http://mail.zope.org/pipermail/zodb-dev/2005-December/009560.html
Fascinating! I didn't know "plagiarism" was French for "open source" ;-)
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.or
Tim Peters wrote:
[Dennis Allison]
I have yet to figure out how to map a TransientObject "state" back
to the object it represents, but it clearly is possible.
I didn't see a response to that bit yet, so: "the state" of an object P is
whatever P.__getstate__() returns. Given such a return val
On 12/16/05, Dennis Allison <[EMAIL PROTECTED]> wrote:
> MAYBE CONFLICTS AND THEIR RESOLUTION ARE NOT THE ROOT CAUSE OF THE SESSION
> VARIABLE PROBLEM. The observed problem is that session variables suddenly
> disappear.
Perhaps your app is tripping over some bug in conflict handling. But
I'd say
Zope 2.8.4, ZODB 3.4.2
Chris,
I'm pretty sure that I mentioned having done that in one of my postings.
I have followed your recommendations, but the problem remains. (um...
persists )
The systems are running a Zope/ZEO combination with a store configuration
of:
#
# Temporary storage d
On 12/15/05, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Chris McDonough]
> > Note that changing the transientobject conflict resolution algorithm
> > won't get rid of all write conflict errors, because the BTree-based
> > indexes in the transient object container will still conflict during a
> > "buc
[Chris McDonough]
> Note that changing the transientobject conflict resolution algorithm
> won't get rid of all write conflict errors, because the BTree-based
> indexes in the transient object container will still conflict during a
> "bucket split" and other situations that I can't exactly recall
>
Code would be good.
Note that changing the transientobject conflict resolution algorithm
won't get rid of all write conflict errors, because the BTree-based
indexes in the transient object container will still conflict during
a "bucket split" and other situations that I can't exactly recall
