- 17 Nov, 2016 13 commits
-
-
Kazuhiko Shiozaki authored
/reviewed-on nexedi/zodbtools!1 /see-also nexedi/slapos!116
-
Kirill Smelkov authored
This is enhanced version of ZODB original scripts/analyze.py . Nexedi version was originally developed as part of ERP5 here: https://lab.nexedi.com/nexedi/erp5/commits/master/erp5/util/zodbanalyze It was agreed to move zodbanalyze to zodbutils /see slapos!116
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
* it is faster. * it does not require Products.
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kirill Smelkov authored
(where `python setup.py sdist` puts result tarballs)
-
-
- 16 Nov, 2016 5 commits
-
-
Kirill Smelkov authored
WARNING output format is not stable yet.
-
Kirill Smelkov authored
-
Kirill Smelkov authored
This is a tool to compare two ZODB databases in between tidmin..tidmax transaction range with default range being -∞..+∞ - (whole database). For comparision both databases are scanned at storage layer and every transaction content is compared bit-to-bit between the two. The program stops either at first difference found, or when whole requested transaction range is scanned with no difference detected. Database storages are specified in files with ZConfig-based storage definition, e.g. %import neo.client <NEOStorage> master_nodes ... name ... </NEOStorage> Please see nexedi/neoppod!4 for one of possible contexts. The tool is generic though and is not NEO-specific. It should be able to even check two different storages like ZEO & NEO, or FileStorage and NEO etc and thus can be handy. TODO tests
-
Kirill Smelkov authored
-
Kirill Smelkov authored
Project to be a place for various ZODB utilitieis. Jim Fulton suggested to have it separate from ZODB/scripts/ [1] and now we have it here. [1] https://github.com/zopefoundation/ZODB/pull/128#issuecomment-260970932
-