When using M1 i could reinstall the extension (launch setup/upgrade) just deleting the extension recording from the core_resource table. During the second Magento address (or after cache refreshing) the extension executed all the files properly beginning from the 0 versions.

Unfortunately, I could not find detailed information on how to reinstall the extension previously installed on my Magento 2. Maybe somebody faced the same issue and knows the plan of action for reinstalling the extension on Magento 2 and could help. Your help will be highly appreciated.

1. I've got module v. 2.0.0 successfully installed with my own tables
2. I've deleted the tables manually from the database
3. I've got module v. 2.0.0 without tables

module:uninstall is intended to be used, only if you are absolute certain, that the module won't be used any longer. However, other modules may have dependencies on the module that is to be removed. Hence we use composer remove, which calculates dependencies and removes code of the module from the file system. We cannot uninstall a module that is NOT installed via composer, since there is no way for us to know about dependencies in such a situation. It is risky to remove data and code in such a case. Hence, it is recommended that for modules NOT installed via composer, manual clean up of the database and the filesystem is necessary. In module enable/disable, the code is never removed from the filesystem, so that it can be used if required at a later time. Hence, it is not removed from the setup_module table.

When using M1 i could reinstall the extension (launch setup/upgrade) just deleting the extension recording from the core_resource table. During the second magento address (or after cache refreshing) the extension executed all the files properly beginning from the 0 version.

Unfortunately i could not find the detailed information on how to reinstall the extension previously installed on my magento 2. Maybe somebody faced the same issue and knows the plan of actions for reinstalling the extension on magento 2 and could help. Your help will be highly appreciated.

1. I've got module v. 2.0.0 successfully installed with own tables
2. I've delete the tables manually from the database
3. I've got module v. 2.0.0 without tabels

module:uninstall is intended to be used, only if you are absolutely certain, that the module wont be used any longer. However, other modules may have dependencies on the module that is to be removed. Hence we use composer remove, which calculates dependencies and removes code of the module from the file system. We cannot uninstall a module that is NOT installed via composer, since there is no way for us to know about dependencies in such a situation. It is risky to remove data and code in such a case. Hence, it is recommended that for modules NOT installed via composer, manual clean up of the database and filesystem is necessary. In module enable/disable, the code is never removed from the filesystem, so that it can be used if required at a later time. Hence, it is not removed from the setup_module table.

When using M1 i could reinstall the extension (launch setup/upgrade) just deleting the extension recording from the core_resource table. During the second magento address (or after cache refreshing) the extension executed all the files properly beginning from the 0 version.

Unfortunately i could not find the detailed information on how to reinstall the extension previously installed on my magento 2. Maybe somebody faced the same issue and knows the plan of actions for reinstalling the extension on magento 2 and could help. Your help will be highly appreciated.

1. I've got module v. 2.0.0 successfully installed with own tables
2. I've delete the tables manually from the database
3. I've got module v. 2.0.0 without tabels

module:uninstall is intended to be used, only if you are absolutely certain, that the module wont be used any longer. However, other modules may have dependencies on the module that is to be removed. Hence we use composer remove, which calculates dependencies and removes code of the module from the file system. We cannot uninstall a module that is NOT installed via composer, since there is no way for us to know about dependencies in such a situation. It is risky to remove data and code in such a case. Hence, it is recommended that for modules NOT installed via composer, manual clean up of the database and filesystem is necessary. In module enable/disable, the code is never removed from the filesystem, so that it can be used if required at a later time. Hence, it is not removed from the setup_module table.

When using M1 i could reinstall the extension (launch setup/upgrade) just deleting the extension recording from the core_resource table. During the second Magento address (or after cache refreshing) the extension executed all the files properly beginning from the 0 versions.

Unfortunately, I could not find detailed information on how to reinstall the extension previously installed on my Magento 2. Maybe somebody faced the same issue and knows the plan of action for reinstalling the extension on Magento 2 and could help. Your help will be highly appreciated.

1. I've got module v. 2.0.0 successfully installed with my own tables
2. I've deleted the tables manually from the database
3. I've got module v. 2.0.0 without tables

module:uninstall is intended to be used, only if you are absolute certain, that the module won't be used any longer. However, other modules may have dependencies on the module that is to be removed. Hence we use composer remove, which calculates dependencies and removes code of the module from the file system. We cannot uninstall a module that is NOT installed via composer, since there is no way for us to know about dependencies in such a situation. It is risky to remove data and code in such a case. Hence, it is recommended that for modules NOT installed via composer, manual clean up of the database and the filesystem is necessary. In module enable/disable, the code is never removed from the filesystem, so that it can be used if required at a later time. Hence, it is not removed from the setup_module table.

module:uninstall is intended to be used, only if you are absolutely certain, that the module wont be used any longer. However, other modules may have dependencies on the module that is to be removed. Hence we use composer remove, which calculates dependencies and removes code of the module from the file system. We cannot uninstall a module that is NOT installed via composer, since there is no way for us to know about dependencies in such a situation. It is risky to remove data and code in such a case. Hence, it is recommended that for modules NOT installed via composer, manual clean up of the database and filesystem is necessary. In module enable/disable, the code is never removed from the filesystem, so that it can be used if required at a later time. Hence, it is not removed from the setup_module table.

module:uninstall is intended to be used, only if you are absolutely certain, that the module wont be used any longer. However, other modules may have dependencies on the module that is to be removed. Hence we use composer remove, which calculates dependencies and removes code of the module from the file system. We cannot uninstall a module that is NOT installed via composer, since there is no way for us to know about dependencies in such a situation. It is risky to remove data and code in such a case. Hence, it is recommended that for modules NOT installed via composer, manual clean up of the database and filesystem is necessary. In module enable/disable, the code is never removed from the filesystem, so that it can be used if required at a later time. Hence, it is not removed from the setup_module table.