Having just noticed that removing an index gives a warning asking if I am absolutely sure I want to delete the index, it made me remember that in testing a while back I noticed deleting an entire database table didn't ask for anything, no password confirmation, no time-delay, no anything; it was gone instantly. I think considering the type of catastrophe this can cause for certain implementations it would be prudent to have an option for developers to 'lock' a database table - flagging it for various security measures such as:
-ask for confirmation before flagging for deletion
-require password before proceeding
-delay a specified amount of time (days+) before the actual deletion takes place, with option for cancel anytime before.
3rd option being the most important, I'm sure anyone from YGN/IO can imagine the scenarios this would mitigate or prevent.
I say this be an option because in testing/learning some developers may prefer the fast and easy approach (but even then I think a simple confirmation is needed)
Please consider this as a security feature,
and thanks for reading.