The table KiB information is a waste of space. Who cares if the table is 32.2 KiB or 74.6 kiB.
Use that space to implement a locking mechanism to prevent unwanted 'drops'. That functionality is needed in HeidiSQL.
I just deleted by mistak a table. It will take me significant effort to get that table back. Why are you reluctant to add a lock mechanism?
It is your fault for not working with (or having) backups. It is your fault for ignoring the in-place warnings.
So tell me, what would yet another mechanism change ? Surely it would not cure stupid, so why bother?
Have you guys never studied probability? The probability of dropping a table at any given time is very low. Given enough the though and you will mistakenly drop a table. Why not provide the feature and let people hide it or ignore it if they don't want to use it?
Honestly, have you never been working late at night and really tired? Seems pretty intuitive to me.
Please login to leave a reply, or register at first.