Table/column deletion checks and disabling fetched external table deletion #3477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR brings an update to the UI to make sure the user is aware of the risks when deleting a table or a column, making sure that the user is aware of the risk attached with deleting them. For now I have also disabled the ability to delete tables which weren't created by Budibase in external SQL tables as this has quite a bit of risk attached to it as well. If we want to enable this again it is a very simple change, but this just makes sure that we are aware of which tables were created through Budibase and which ones were imported.
Screenshots
Table deletion:
![image](https://user-images.githubusercontent.com/4407001/142890460-ada90d24-8992-4c5c-b7e8-956ba5bd3baa.png)
Column deletion:
![image](https://user-images.githubusercontent.com/4407001/142890550-c43b2842-ddf7-4f0b-b057-772f07eb51e7.png)