Module Loader - Uninstalling custom module; DB tables still there

Hello - 

First, thank you to everyone who's helped answer questions so far. Not a Sugar novice but with new capabilities, there's a learning curve of what's possible and not.  So, thank you!

We had designed several custom modules and loaded them successfully and used them.  Because of the way we structured them, we decided to uninstall/delete them in module loader.  

When we look in Sugar (Studio, etc.) all reference to the modules is gone (YAY).  When we look in the database (MySQL), the database tables are still there (both for the modules themselves and the relationships to modules like accounts).  We specifically checked the option to remove the database tables (it's checked by default and we verified that's what we wanted).  However, they remain.

During the deletion, we had the log displayed and there were no errors listed as it went.  In the Sugar log, we see no listed errors.

Two questions:

1. Anyone have any idea what might have happened?  Don't see anything on this site or in any Google searches.

2. Can we drop the database tables that are no longer needed (the module table, the module_cstm table, the relationship tables)?

Thank you very much.

Bob

Parents
  • Hi ,

    Uninstalling from module loader will only attempt to remove tables the module package originally installed. Studio actions such as creating custom relationships will require cleanup if the relationships were not deleted via Studio before performing the module uninstall. Since you mentioned a _cstm table, it sounds like there was additional changes made in Studio after the original install. For Studio-created relationships, there may be artifact files remaining under the ./custom/Extension/ directory that would be best to be removed.

    As for the database tables, there should be no harm in removing those tables.

Reply
  • Hi ,

    Uninstalling from module loader will only attempt to remove tables the module package originally installed. Studio actions such as creating custom relationships will require cleanup if the relationships were not deleted via Studio before performing the module uninstall. Since you mentioned a _cstm table, it sounds like there was additional changes made in Studio after the original install. For Studio-created relationships, there may be artifact files remaining under the ./custom/Extension/ directory that would be best to be removed.

    As for the database tables, there should be no harm in removing those tables.

Children
No Data