Hi,

When upgrading from 5.0 -> 5.1 the sort order of some german characters was modified, which meant indexes had to be rebuilt (they are in sorted order after all). The mysql_upgrade would suggest a table rebuild (ALTER TABLE xyz ENGINE=INNODB) or dump/restore for every affected table. I was a consultant during this time, and I can't tell you how many tables I had to rebuild. Thousands to say the least. Yuck.

--Greenlion

On Wed, Oct 12, 2016 at 10:01 AM, Reindl Harald <h.reindl@thelounge.net> wrote:

Am 12.10.2016 um 15:53 schrieb Justin Swanhart:

Also having to dump/restore to go from 10.2 to 10.3 tables is a PITA

it's a simple no-go and the answer to "should i use postgre or mysql/mariadb" is always "stay away from postgre, while it got better you need to dump your data and import them again still way too often while our mysql tables where created 2002 and now running on MariaDB 10 without doing such a bullshit a single time"

Remember how awful it was to migrate all those BDB tables to InnoDB? Or
even just how frustrating it was when UTF8_GENERAL_CI changed the umlaut?

when did something change umlauts?

as charsets where introdcued with MySQL 5.0 it was a simple script just to add the correct charset information that it is *not* UTF8 to 5000 tables with not a single char damaged and since we are located in austria üöäß are very common

_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp