Hello,
zc.demostorage2 assumes that the tpc_begin() of its underlying
storages takes three parameters (transaction, tid, status), while both
MappingStorage and IStorage only know about the first two.
This strikes me as risky, and it does indeed break, for example when
trying to use a DemoStorage
ZODB Developers,
Can you please tell me what I am doing wrong in my first simple attempt to
make use of ZEO. My ZODB and ZEO are both the same version (3.6.0).
First, I start my ZEO server and it looks like it starts properly:
python2.4 /usr/lib/python2.4/site-packages/ZEO/runzeo.py -a
On Thu, Nov 26, 2009 at 1:51 PM, tsmiller tsmil...@gnixterhouse.com wrote:
Laurence,
Thank you for your very quick reply. I did as you suggested and now the
ConflictError is now handled. And that is a most excellent thing because
now ConflictError is raised every time. So it still seems to
James,
You were right. I moved the assignment into the inner loop where is is
reassigned each time after the abort. However, if I do not put the abort()
in, then the ZODB comes back with a ConflictError and actually dies with a
TransactionFailedError. The commit() is the purpose of the entire
Hi,
On 11/26/2009 10:08 PM, James Bergstra wrote:
On Thu, Nov 26, 2009 at 1:51 PM, tsmillertsmil...@gnixterhouse.com wrote:
Laurence,
Thank you for your very quick reply. I did as you suggested and now the
ConflictError is now handled. And that is a most excellent thing because
now
Christian,
Thanks. How painfully obvious. I have written the words
'transaction.begin()' about a thousand times or so! But I get
discombobulated when I start looking at something new ( ZEO ) and forget the
obvious. Final code for this little test that works perfectly:
while True:
Hi,
On 11/26/2009 10:55 PM, tsmiller wrote:
Christian,
Thanks. How painfully obvious. I have written the words
'transaction.begin()' about a thousand times or so! But I get
discombobulated when I start looking at something new ( ZEO ) and forget the
obvious. Final code for this little
