[CWB] [ cwb-Bugs-2954499 ] Deleting a corpus doesn't drop all related MySQL tables

SourceForge.net noreply at sourceforge.net
Sun Feb 28 19:03:09 CET 2010


Bugs item #2954499, was opened at 2010-02-18 22:49
Message generated for change (Comment added) made by andrewhardie
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=722303&aid=2954499&group_id=131809

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CQPweb
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 6
Private: No
Submitted By: Stefan Evert (schtepf)
Assigned to: Andrew Hardie (andrewhardie)
Summary: Deleting a corpus doesn't drop all related MySQL tables

Initial Comment:
My corpora are all pre-indexed in the CWB, so CQPweb cannot overwrite or delete the original corpus files. In this case, it fails with file access error messages and stops halfway through the corpus deletion.  If I change the registry entry to point to a bogus data directory that CQPweb has permissions to remove, corpus deletion goes through without error.  There are still many database tables left in MySQL, notably all the freq_corpus_* tables and freq_text_*.  I'm not sure if there are entries in some other tables that should be deleted as well.

----------------------------------------------------------------------

>Comment By: Andrew Hardie (andrewhardie)
Date: 2010-02-28 18:03

Message:
The attempt to delete the original files seems to have been due to an
out-of-date admin-lib.inc.php and should not now occur.

Failure to delete all tables, however, was actually a bug, now fixed. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=722303&aid=2954499&group_id=131809


More information about the CWB mailing list