On Tue, Feb 16, 2010 at 06:11:13AM +0000, Duncan wrote: > > - If you actually ran mysqld as your own user (Akonadi w/ internal MySQL > > instance), use the mysql_upgrade with suitable parameters to connect > > to the database (as to what those are, you're the one running it, not > > me). > It's automagic from here. I just run kde. What it does, I don't know. I > just don't want it to break! (And upgrade implications will get worse > with kde 4.5 in August, as kmail will be depending on it then, and users > tend to get rather cross when their mail store gets hosed! With 4.4, it's > mainly the address book.) All of that is under the Akonadi side of KDE. I really don't think storing mail inside MySQL is going to be a good idea.
> >> Perhaps a note for kde users telling them where their databases are > >> located so they /can/ back them up, etc.) > > I've got no idea where they are located, I just focus on MySQL itself. I > > wasn't even aware of Akonadi's usage until a couple of weeks ago. > What I was suggesting, between the lines, is to coordinate with the kde > project. They may want to create their own upgrade document, which might > be listed in the news release or in a separate one (testing for both mysql > and kde). Hopefully they reply to this thread with whatever their > concerns there might be. I announced it 2 weeks ago, on February 1st, Message-Id: robbat2-20100201t012126-6370737...@orbis-terrarum.net I just hadn't gotten to actually doing it yet due to travel and getting sick on my way home (and Delta doing everything in their power to screw things up, I still haven't got one of my pieces of luggage back yet). As soon as the 72 hours on this news announcement are done, I'm going to be unmasking it. I do expect most of the breakage to come from the client libraries, and NOT any actual data storage issues. If MySQL detects that it's not safe to access a table, it does give you a suitable error to repair the table. mysql_upgrade is actually really just running 'CHECK TABLE ... FOR UPGRADE;' && 'REPAIR TABLE ...' on tables with something that needs to change. Doing a 'REPAIR TABLE ...' globally will cover you if you don't have any other way to issue the check statements manually. That is of course me assuming that you have a way to issue 'REPAIR TABLE ...', because that's a critical MySQL command for the DBA/user to know in managing their data. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
