Feature #2465
RCP: 0.7.9, Management of corrupted binary corpora
| Status: | New | Start date: | 10/30/2018 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Corpus | Spent time: | - | |
| Target version: | - |
Description
TXM should produce a comprehensible error message and abort loading if a binary corpus file does not correspond to the specified corpus.
As of TXM 0.7.9, when loading a binary corpus where the archived files are not wrapped into a directory bearing the corpus names results in destruction of all the previously loaded or imported corpora (because the content of "corpora" directory is purged ans the new corpus files are written directly into that directory.
The warning displayed before loading just says "The corpus already exists. Do you want to replace it?" (the corpus name is empty)
Related issues
History
#1 Updated by Serge Heiden almost 2 years ago
See also Bug #974 TBX: 0.7.6, corpus load abort causes corrupted corpus ticket solution.