-
Notifications
You must be signed in to change notification settings - Fork 64
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
Migration documentation incomplete #207
Comments
Can I fix this by adding the note below to Migrating to Galera Cluster -> Data Migration, where the command above is mentioned: Note! |
@kirjaamo where do we specify this? esp. the "--skip-create-options" ? do we even have a document re: migrating from myisam to innodb? can i read the whole thing in context? |
But we do not have a document re: migrating from myisam to innodb |
@byte You are right, we do not have a document re: migrating from myisam to innodb. Can I use the link below to create that? |
Where it is specified
$ mysqldump -u root -p --skip-create-options --all-databases > migration.sql
should also be a note that this export can break everything in the new database. For example, if you have any fields as PK with auto_increment, that would not be imported correctly. There could be a lot of extra infos from the db that would not be copied to the galera cluser. IMO the preferred way to export from MyISAM to INNODB would be a normal export and manually change the ENGINE. Cheers.The text was updated successfully, but these errors were encountered: