On Tue, May 18, 2010 at 1:14 PM, Ryan Noon rmn...@gmail.com wrote:
Hi All,
I converted my code to use LOBTrees holding LLTreeSets and it sticks to the
memory bounds and performs admirably throughout the whole process.
Unfortunately opening the database afterwards seems to be really really
Does RelStorage handle concurrent writes correctly? This is probably
so obvious as to ask if the sky is blue, but I couldn't tell from the
documentation if I could setup multiple Zope (Plone in my case)
instances all using RelStorage to talk to the same database without
incident.
relstorage
I'm completely new to Zope, but from what I've been able to find it
looks like ConflictErrors are simply a side effect of optimistic
concurrency control, not unlike conditional PUTs in HTTP. This is
exactly the behavior I would expect.
Thanks for the quick response,
- Zack Spencer
On Tue, May
On 05/18/2010 10:08 PM, Jim Fulton wrote:
The design of ZODB views pickles as opaque to storages. Storages
primarily store strings. I have always assumed that writing wrapper
storages for compression or encryption would be easy. I was wrong. :)
Storages sometimes need to know about pickles:
On 05/18/2010 01:40 PM, Zack Spencer wrote:
I'm completely new to Zope, but from what I've been able to find it
looks like ConflictErrors are simply a side effect of optimistic
concurrency control, not unlike conditional PUTs in HTTP. This is
exactly the behavior I would expect.
Exactly.
See: http://pypi.python.org/pypi/ZODB3/3.10.0b1
3.10.0 is now feature frozen.
Jim
--
Jim Fulton
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
