dropping a table leaves view redundant

One of our developers dropped a table from the database, the table called table1. Some weeks later we took a mysqldump and restore the dump back to a test machine and the restore process breaks. Developer had no idea and DBA had to step in.

Actually the view was referencing to the table1 which no longer exist and quite rightly the restore had to break. I was wondering if it is possible that when we drop a table the drop statement should fail if a view exist.