module uninstall: module creators should provide sql database table removal scripts for uninstall
Module developers who create modules that modify the drupal database should provide a .mysql file that can be used to remove all the database records and tables associated with their module during uninstallation.
This is particularly important when bugs or incompatibilities arise.
EXAMPLE:
This occurred for me after installing the privatemsg module and then the relationship module.
The second installation broke BOTH modules.
Even after 'uninstalling' both of them, their database modifications still exist.
The corrupted database continues to produce error messages!
Re-installing privatemsg alone, without relationship, fails because the drupal database is now corrupted somehow.
complete uninstall .mysql files would help and would help document what needs to be removed from the drupal database.
you're right!
you're right! My experiences are the same than yours.
I'v found eg. taxonomy_acces <--> evaulation confict and thats why I can't remove evaulation module without drupal a defect.
http://drupal.org/node/48240
Amen to that.
Amen to that.
I agree
Yepp!
Agree too
Take a look at the system table: it holds the state of the different modules.
If the module is still in the system table, Drupal will think that the module is still installed.
I agree that a module uninstaller would be a useful tool.
That would be really sweet.
That would be really sweet.
I agree. And even if you
I agree.
And even if you dont run into problems like that - you dont wanna have a messed up database (when testing some modules that you dont need anymore for example)