|
From: David G. <da...@co...> - 2012-01-13 13:14:28
|
On 13 Jan 2012, at 13:05, Tanstaafl wrote: > On 2012-01-13 7:47 AM, David Goodwin <da...@co...> wrote: >> On 13 Jan 2012, at 12:37, Tanstaafl wrote: >>> Can I simply edit the dump file prior to restoring it? Ie, change the >>> Engine in each of the table definitions from MyISAM to InnoDB? > >> Yes. We don't use any full text indexes so there is no dependency on MyISAM. > > Hmmm... I didn't know of that limitation with InnoDB, I just read > somewhere that InooDB was preferred… > InnoDB is good for tables which have frequent updates and reads. When you update a MyISAM table the entire table is locked - so on a high traffic site reads are delayed. I'd be surprised if there were many Postfixadmin installations which have enough write and read traffic for it to matter which they use. InnoDB is the way forward - MySQL 6(?) will (perhaps does already?) effectively default to using it. I think it recovers better from crashes and supports transactions etc. Postfixadmin doesn't use transactions. > So... maybe I should stick with MyISAM? > >>> As for changing the character set from latin1 to utf8... can I do >>> it the same way as described above (simply edit the dump file >>> before restoring)? > >> No. Any utf-8 characters already in there will be stored in a weird >> encoding. If you have no existing UTF8 characters in your data then it >> would work. > > Ok, thanks... is there a way to test for existing utf8 characters? I'm > assuming I don't, since this database has apparently always been in > latin1 format… > Not that I know of. > Last... what is *recommended* for postfixadmin? > If it's working, don't "fix" it….. David. |
