Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mysql.dump using MyISAM #29

Open
GoogleCodeExporter opened this issue Dec 7, 2015 · 1 comment
Open

mysql.dump using MyISAM #29

GoogleCodeExporter opened this issue Dec 7, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

 Hi,

What steps will reproduce the problem?
1. Look at src/dump.mysql

What is the expected output? What do you see instead?
ENGINE=MyISAM, should be ENGINE=InnoDB

What version of the product are you using? On what operating system?
Browsing the GIT trunk, r67.

Please provide any additional information below.
Is there a reason behind using MyISAM? InnoDB/XtraDB seems to be the more 
future-proof choice.


Cheers, Nafallo

Original issue reported on code.google.com by Nafall...@gmail.com on 23 Apr 2013 at 6:21

@GoogleCodeExporter
Copy link
Author

Good point;

I had a go at changing it, however, when I do we can no longer pass our unit 
tests when using mysql.  I am unsure exactly why changing the table type would 
have this affect, so have left it at MyISAM for right now.

Original comment by glen.ogilvie@gmail.com on 6 Sep 2013 at 9:59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant