|
RE: BTrees did it, was: conflict resolution for PersistentList: msg#00146web.zope.zodb
[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. _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@xxxxxxxx http://mail.zope.org/mailman/listinfo/zodb-dev |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: BTrees did it, was: conflict resolution for PersistentList: 00146, Tim Peters |
|---|---|
| Next by Date: | CIAL~1S & LEVI~TRA : E*n1arging, s-trengthening and developing your P_EN1S n'atura1ly: 00146, Werner Nair |
| Previous by Thread: | RE: BTrees did it, was: conflict resolution for PersistentListi: 00146, Tim Peters |
| Next by Thread: | Re: conflict resolution for PersistentList: 00146, Syver Enstad |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |