Execute interdependent views from mysqldump backup
===

*mysqldump* creates a dump with the tables (and views) listed alphabetically. When there are foreign key relationships between the tables this is not very convenient, however, the problem is easily resolved by running: 

    SET FOREIGN_KEY_CHECKS=0;

I have a situation whereby the view, vwapple, is dependent on the view, vworange, say. With the mysqldump, vwapple is listed and executed before vworange, which is problematic as we'll get a "view vworange does not exist" error message. <br />

How is this situation solved? Do views have a similar solutions as tables have? Or is it better to make each view independent just to get round this problem? <br />
 
NOTE <br />
I'm restoring the database using a python script. Each view and table is in its separate .sql file as I want to source control each database object independently.