Question on MySQL database structure: Why 3 MyISAM tables?

[jamesbond]

[AngryChris]

[erikbennett]

I'm using 1.9 (release, not trunk) and actually just recreated my database for other, unrelated reasons. I can confirm that they are still present in my database.

[feader]

[jamesbond]

The fact that both types of tables (MyISAM and InnoDB) are used concerns me because it makes creating backups of the database quite complicated. With MySQL, there are different approaches to backup both types of tables (mysqldump needs different parameters) as discussed and .

It would be much easier if only one type of tables was be involved.

[fox]

You don't need to backup counters and tbqh I never had this problem, mysqldump always seemed to backup everything correctly for me.

[sleeper_service]

[fox]

I'd like to post an obligatory lol @ dealing with mysql while caring about any sort of data integrity whatsoever.

[sleeper_service]

[jamesbond]

[sleeper_service]

[AngryChris]

[sleeper_service]

isn't there a way to convert a myisam table to innodb?

[AngryChris]

[fox]

I'll update the schema files for those tables to use innodb. Keeping those tables as isam is not required or anything, I just figured it would be a bit faster.

e: Since myisam is not specified explicitly in the dable definition, I'm not sure if making a migration for this is a good idea - what if it's innodb already or something? We don't want database upgrade scripts to break, this is confusing for people.