Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
- abort the current transaction
- sync its database connection (to pick up the changed objects)
I'm pretty sure the abort has done the sync for quite some time now...
Nope, see:
Tres Seaver wrote:
- abort the current transaction
- sync its database connection (to pick up the changed objects)
I'm pretty sure the abort has done the sync for quite some time now...
Chris
--
Simplistix - Content Management, Zope Python Consulting
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
- abort the current transaction
- sync its database connection (to pick up the changed objects)
I'm pretty sure the abort has done the sync for quite some time now...
Nope, see:
Hi all
I run my script foo.zctl with zopectl run foo.ctl param1 param2.
This script operates on a large ZODB and catches ConflictErrors
accordingly. It iterates over a set, updates data and commits the
transaction every 100 iterations. But I've noticed two things:
1. ConflictErrors are never
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hedley Roos wrote:
Hi all
I run my script foo.zctl with zopectl run foo.ctl param1 param2.
This script operates on a large ZODB and catches ConflictErrors
accordingly. It iterates over a set, updates data and commits the
transaction every 100
Hi Tres!
Thanks for the tips. I managed to get my script running in batches and
with manual intervention. When in future I encounter the same problems
I'll report back to this thread.
Hedley
___
Zope maillist - Zope@zope.org