[ZODB-Dev] BTrees did it, was: conflict resolution for PersistentList

[Tim Peters]

[Diez B. Roggisch]
> ok, I tried the btrees, and they seem to do what I want.

Good!

> Gotta figure out how to create nice keys, but thats a minor problem.

Also a pretty frequent problem.  It Would Be Nice If we grew something in
ZODB to help that.  Concrete proposals encouraged.

> Thanks to all helping me here. Of course I'm still willing to work on that
> conflict problem if its important to people. Just ask.

Thanks, but I believe Chris and I convinced each other that what you were
seeing wasn't unexpected.  Especially since it turned out you were using a
ZODB 3.3 alpha release, you had "multiversion concurrency control" by
default, which should have prevented read conflicts.  That ratchets the odds
that the errors getting suppressed were raised by commit(), and losing
changes when ignoring commit() exceptions is an expected outcome.