Re: Changing storage engine in dump file.
- Date: Wed, 12 Aug 2015 19:09:29 +0530
- From: Pothanaboyina Trimurthy <skd.trimurthy@xxxxxxxxx>
- Subject: Re: Changing storage engine in dump file.
it is better to take the dump as it is on the master, restore it on the
salve and then change the storage engine through alter table commands that
will be the right way of doing and you could see any issues while
converting from MyISAM to InnoDB.
On Wed, Aug 12, 2015 at 6:51 PM, Johan De Meersman <vegivamp@xxxxxxxxx>
> ----- Original Message -----
> > From: "geetanjali mehra" <mailtogeetanjali@xxxxxxxxx>
> > Subject: Changing storage engine in dump file.
> > Is there any implications in doing so. Is this approach correct? Will I
> > face any problem in syncing the slave?
> The first thing that occurs to me, is that the maximum key lenght for
> MyISAM is 1000 bytes, but for InnoDB it is only 786 bytes...
> Depending on your server version, InnoDB may not yet have fulltext
> indices, and even if it does, the behaviour is different from the MyISAM
> You are likely to run into a myriad of tiny little differences, and it
> seems to me like a fairly bad plan. Why do you want this?
> Unhappiness is discouraged and will be corrected with kitten pictures.
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql
Mobile : +91 97397 64298