Bug #2819
Mis à jour par Serge Heiden il y a plus de 5 ans
When a corpus is removed, the associated knowledge repository (KR) is not removed. If the corpus is re-imported, the old KR is used instead of a fresh new empty KR.
The Corpus<->KR relation life cycle is the following:
* a corpus is imported and a fresh empty KR is available
* a corpus is re-imported and a reused empty KR is available
* a corpus is updated and its KR is preserved
h3. Solution
Catch the CQP "Corpus delete" event and remove the corpus KR from the KRs database.
In both TXM 0.8.0 and TXM 0.8.1beta, the KR is removed but changes are only visible after restarting TXM.
The corpus update process raises a "CQP corpus delete" event -> the KRs database must check if the corpus is being updated, if true the KR must not be deleted.
The Corpus<->KR relation life cycle is the following:
* a corpus is imported and a fresh empty KR is available
* a corpus is re-imported and a reused empty KR is available
* a corpus is updated and its KR is preserved
h3. Solution
Catch the CQP "Corpus delete" event and remove the corpus KR from the KRs database.
In both TXM 0.8.0 and TXM 0.8.1beta, the KR is removed but changes are only visible after restarting TXM.
The corpus update process raises a "CQP corpus delete" event -> the KRs database must check if the corpus is being updated, if true the KR must not be deleted.