Bug #1516
Mis à jour par Matthieu Decorde il y a presque 10 ans
I already have a VOEUX corpus in TXM before upgrading to 0.7.7.
When TXM is upgraded to 0.7.7, I see two instances of the VOEUX corpus, one at the top of the list, and the second at the bottom (or near the bottom).
These two instances correspond to the previous version of VOEUX corpus : it is smaller than the one delivered with TXM 0.7.7 (T=61102 vs T=61162) and has no mention of date, author, etc. at the beginning of the Description.
These two instances look like two views of the same object : every modification on one is also applied on the other one. Except deletion : deleting the "bottom" view of VOEUX doesn't suppress the "top" view (but this top view "is not ready").
If one delete every view of VOEUX and then load again this corpus, one gets a warning, like "Le corpus voeux existe déjà".
h3. Solution
MD: due to corpus history there are corpus directories named in uppercase end corpus directories names in lowercase that can load *CQP corpus* with the same name.
The solution is to prevent loading corpus with the same name (lower or upper cased). The corpus less recent is not loaded and removed from the loaded corpus list (in the "$TXM/workspaces/default.xml" file).
Note: the files are not removed from disk.
This does not solve the CQP corpus loaded. A corpus should indicate exactly which CQP corpus it needs neds to load in CQP. Thus we should no more use the "$TXM/registry" directory and concat registry paths with ";" (Windows) or ":" (Unix) when we start.
Note: ask Java the right path separator to use
When TXM is upgraded to 0.7.7, I see two instances of the VOEUX corpus, one at the top of the list, and the second at the bottom (or near the bottom).
These two instances correspond to the previous version of VOEUX corpus : it is smaller than the one delivered with TXM 0.7.7 (T=61102 vs T=61162) and has no mention of date, author, etc. at the beginning of the Description.
These two instances look like two views of the same object : every modification on one is also applied on the other one. Except deletion : deleting the "bottom" view of VOEUX doesn't suppress the "top" view (but this top view "is not ready").
If one delete every view of VOEUX and then load again this corpus, one gets a warning, like "Le corpus voeux existe déjà".
h3. Solution
MD: due to corpus history there are corpus directories named in uppercase end corpus directories names in lowercase that can load *CQP corpus* with the same name.
The solution is to prevent loading corpus with the same name (lower or upper cased). The corpus less recent is not loaded and removed from the loaded corpus list (in the "$TXM/workspaces/default.xml" file).
Note: the files are not removed from disk.
This does not solve the CQP corpus loaded. A corpus should indicate exactly which CQP corpus it needs neds to load in CQP. Thus we should no more use the "$TXM/registry" directory and concat registry paths with ";" (Windows) or ":" (Unix) when we start.
Note: ask Java the right path separator to use