Switching from MyISAM to InnoDB
Posted: Thu Mar 11, 2010 8:52 am
I have 20 or so tables used by a maintenance management system. Aerospace has so many caveats and exceptions to the rule of thumb, most of these tables are to accomodate these weird exceptions. Lots of many to many relationships.
It's very easy to lose yourself in the existing table schema, without first mapping out the relationships between various tables.
SqlYog has a schema diagram tool which will build a visual reference for you, BUT, it seems to assume InnoDB is used.
So I am starting to think:
1. Transactional support would be a bonus and make twice daily backups less critical
2. Foriegn key associations will let diagramming tools to build the map for me saving me tonnes of time (not to mention new developers)
What I would like to know, is whether forign key constrainst in InnoDB will have cascading deletes? When I remove a master record will all of it's associated tables/records be deleted as well? Will switching to InnoDB cause any issues, other than slightly less performance.
Cheers,
Alex
It's very easy to lose yourself in the existing table schema, without first mapping out the relationships between various tables.
SqlYog has a schema diagram tool which will build a visual reference for you, BUT, it seems to assume InnoDB is used.
So I am starting to think:
1. Transactional support would be a bonus and make twice daily backups less critical
2. Foriegn key associations will let diagramming tools to build the map for me saving me tonnes of time (not to mention new developers)
What I would like to know, is whether forign key constrainst in InnoDB will have cascading deletes? When I remove a master record will all of it's associated tables/records be deleted as well? Will switching to InnoDB cause any issues, other than slightly less performance.
Cheers,
Alex