Hi,

In the end of May we had issue with a BaseX release that was corrupting our DBs. We were able to identify this pattern:

1) Update/insert @status on the root element of multiple files. Eveything seems fine here, but something occured that made the DB unstable. We can read data without problem. 2) Change the status a second time, DBs gets corrupted.

We didn't track all operations that occured during that period, but now that we are running a new translation process. We are updating the various language DBs and we are ovewhelmed by corrupted DBs. We thought we had rolled back all the problematic DBs, and apparently we missed some as issues are popping here and there.

I am writing with the hope that you remember an issue with the end of May release and that you can send details on tracking issues before they show up and/or know of a way to resolve the issue before the second run of updates. Rolling back means that we lose a full run of translation and we have nearly 30 languages, which means 30 DBs, so it's not a small job to roll them back and run translation again. And once a DB is corrupted, I can't even open it.

Any clue would help.

Thanks,

France