Hi there,
I think there is no way of doing this but it is worth posting it anyway.
When I do a dump to export a database, mysql put all tables in alphabetical order
articles
brokers
cities
....
login
....
users
Now, many of my tables are InnoDB;
Example: my login table is InnoDB with a foreign key to the USERs table, therefore, when I restore the database it gives me an error in creating the table because the users table does not yet exists.
Is there a way of avoiding to manually modify the dump script moving tables around o rinserting 'if exist' options?
This is becoming an issue as our system is composed by over 100 tables 60 of which is not in the correct place in the dump and has to be moved around every time.
Thank you
Qatqat The reason why my girlfriend can read my thoughts is because mine are properly written! (G.Lepore)
I think there is no way of doing this but it is worth posting it anyway.
When I do a dump to export a database, mysql put all tables in alphabetical order
articles
brokers
cities
....
login
....
users
Now, many of my tables are InnoDB;
Example: my login table is InnoDB with a foreign key to the USERs table, therefore, when I restore the database it gives me an error in creating the table because the users table does not yet exists.
Is there a way of avoiding to manually modify the dump script moving tables around o rinserting 'if exist' options?
This is becoming an issue as our system is composed by over 100 tables 60 of which is not in the correct place in the dump and has to be moved around every time.
Thank you
Qatqat The reason why my girlfriend can read my thoughts is because mine are properly written! (G.Lepore)