On 1/18/06, Stefan Guggisberg <[EMAIL PROTECTED]> wrote: > if you're using a transactional pm (e.g. DerbyPersistenceManager) > you should be pretty safe wrt corrupted repository state after abnormal > process termination.
are these pms transactional with regard to external blobs? in other words, if i'm storing an nt:file node with a 5mb file and i cut the power to the machine in the middle of writing the blob to disk, are derby and the blob fs going to be inconsistent? will jackrabbit be able to start up in such a state? does jackrabbit provide a tool to check for and repair inconsistencies?
