If I reset a tenant through the multitenancy page it only deletes the database tables created by the currently enabled modules.
If I enabled a module and then disabled it, the tables it created will not be deleted by a reset and will remain inside the database.
This can be a problem, because if I try to enable again those modules after doing another setup of the resetted tenant I receive an error, caused by the fact that the migrations try to create again some tables that already exist.
If I reset a tenant through the multitenancy page it only deletes the database tables created by the currently enabled modules.
If I enabled a module and then disabled it, the tables it created will not be deleted by a reset and will remain inside the database.
This can be a problem, because if I try to enable again those modules after doing another setup of the resetted tenant I receive an error, caused by the fact that the migrations try to create again some tables that already exist.