Disabling an EPM removes database tables and fields (and counters) it added to an archive #422
Comments
drn05r
changed the title
drn05r
added a commit
that referenced
this issue
Jan 21, 2025
Moves EPM phrases to Bazaar ingredient Removes duplicate Storage::EPM plugin under perl_lib Adds check_symlinks action Allow --force with enable to use new rather than current/saved version of config file
drn05r
added a commit
that referenced
this issue
Jan 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the Bazaar or tools/epm to disable an EPM will not just disable it in the specific repository archive but it will also remove any database tables / fields and counters defined by the EPM. This may be what the sysadmin wants but bad things from not removing these are limited (DB row length too long / too many indexes) are far outweighed by the bad things that do (deleting all the data in the tables/fields deleted).
It should be possible to build into an EPM that on disable it should retain database tables / fields and counters. It should also be possible to override this when using tools/epm at the command line, so you can really delete tables you don't want or not delete tables if you are just temporarily disabling an EPM on an archive.
The text was updated successfully, but these errors were encountered: