This one's less serious if it is what I think it is:
Traceback (most recent call last):
File "bin/zodbconvert", line 24, in <module>
line 89, in main
line 308, in zap_all
line 217, in _rollback_load_connection
_mysql_exceptions.OperationalError: (2006, 'MySQL server has gone away')
My guess is that the zap_all took so long that the server had gone away
by the time the sql statement had be executed.
Still, far from 100% on that but thought I'd let you know.
I also had a segfault trying to do the same conversion which I'm
attributing to the MySQL server being restarted by an overeager DBA
mid-converstion but still, that shouldn't cause a segfault, right?
Simplistix - Content Management, Batch Processing & Python Consulting
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org