RE: directory storage is not responding
"Toby Dickenson" <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb.dirstorage |
|---|---|
| Message-ID | <C9D19A363862284F9FA316375A3638CB03784D@mercury.internal.geminidataloggers.com> |
> I tried removing (--purge zope*) and reinstall from debian unstable > (zope 2.6.4): default instance with Data.fs works. I duplicate the > instance, install dirstorage (1.1.9 this time), create a dirstorage > from the previously working Data.fs, start the instance: it hangs > and looks at invisible butterflies, again. You have a small Data.fs that works, and it makes zope hang when converted to a DirectoryStorage? If you can email me a copy of the Data.fs and tarball of the storage to [email protected], I will see if I can reproduce. Have you any clue about where it is hanging? > Plus, I would really like to explore the possibility to create a Data.fs > from the existing dirstorage: is there a chance this can be done? Im not aware of any code to do that, but it wouldnt be hard. The Full.py history method has all the logic needed for traversing the storage, and FileStorage has a 'restore' method which can be used to insert the data. The only tricky part is that DirectoryStorage history is linked starting with recent history but FileStorage.restore wants old history first, so you need to reverse the transaction order. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com