Alan Runyan wrote at 2008-2-26 13:07 -0600:
...
Most people come at ZODB with previous experience in RDBMS.
How do they map SQL INSERT/UPDATE activities to ZODB data structures?
In a way that does not create hotspot.
I tend to views the objects in an application
as belonging to three types:
Kenneth Miller wrote:
Is there a standard bit of documentation as to how to handle a
ZEO server with multiple clients writing to the same data structure at
the same time?
Not documentation, but there is a standard bit of snark that might be
helpful: don't do that. ;)
In other
Could you provide a bit more guidance? Maybe an example.
Most people come at ZODB with previous experience in RDBMS.
How do they map SQL INSERT/UPDATE activities to ZODB data structures?
In a way that does not create hotspot.
A few years ago people would say pick a BTree implementation that
Alan Runyan wrote:
Could you provide a bit more guidance? Maybe an example.
Here's one: in certain circumstances people want to aggregate lots of
incoming data, but doing the obvious thing of updating a data structure
as new data comes in turns out to be too slow. One way to handle that
All,
Is there a standard bit of documentation as to how to handle a
ZEO server with multiple clients writing to the same data structure at
the same time? Right now I've got my own layer that runs ontop of a
zeo client connection and handles this with ZODB.lock_file, but i
really
Kenneth,
I believe you will want to look into 'conflict resolution'.
Possible source of inspiration:
http://www.zope.org/Documentation/Articles/ZODB2
--
Alan Runyan
Enfold Systems, Inc.
http://www.enfoldsystems.com/
phone: +1.713.942.2377x111
fax: +1.832.201.8856
