Hi, > using what database ? might be a transaction problem... I'm using HSQL.
I get the same error with Informix 7.30 UC4 But I think that the problem come from the FileContentStore. When you do a DELETE on a collection and inside this collection there is a file with a lock, the descriptor store starts by deleting each entry without lock from the database and sends the order to the content store to delete the corresponding content. After that, there is a rollback because one resource is locked. There is no rollback implementation in the FileContentStore and thus the deleted files are lost for ever. At this stage, we have a wrong state between the content and the descriptor store. I try this test: Create a collection Put three resources in this collection Lock a resource Delete the collection After the delete, the state of the database is the same a before the delete. Why is the rollback not implemented in the FileContentStore? Didier -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
