From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NhKSV-0000PA-DD for garchives@archives.gentoo.org; Tue, 16 Feb 2010 10:15:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 70871E09CD; Tue, 16 Feb 2010 10:15:06 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id C8466E09C9 for ; Tue, 16 Feb 2010 10:14:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 7BEAE1B402D for ; Tue, 16 Feb 2010 10:14:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -2.554 X-Spam-Level: X-Spam-Status: No, score=-2.554 required=5.5 tests=[AWL=0.045, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVwysbS0Lmui for ; Tue, 16 Feb 2010 10:14:35 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by smtp.gentoo.org (Postfix) with ESMTP id E296A1B4019 for ; Tue, 16 Feb 2010 10:14:33 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NhKRp-0006dM-0s for gentoo-dev@gentoo.org; Tue, 16 Feb 2010 11:14:29 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Feb 2010 11:14:29 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Feb 2010 11:14:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: News item: MySQL 5.1 bump Date: Tue, 16 Feb 2010 10:14:08 +0000 (UTC) Message-ID: References: <20100216001408.GA346@orbis-terrarum.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: af223b58-5207-4805-8713-b211461534ec X-Archives-Hash: 5880827075b153606ee7b178389f3bd8 Robin H. Johnson posted on Tue, 16 Feb 2010 06:26:03 +0000 as excerpted: > On Tue, Feb 16, 2010 at 06:11:13AM +0000, Duncan wrote: >> 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!=20 >> 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. Me neither, but I'm just a user. >> What I was suggesting, between the lines, is to coordinate with the kd= e >> project. They may want to create their own upgrade document [,etc.] > I announced it 2 weeks ago, on February 1st, Message-Id: > robbat2-20100201T012126-637073772Z@orbis-terrarum.net Is there a bug on it for the KDE folks? Should I open one? I /am/ going to post a message to the kde lists (where I'm a regular)=20 asking about mysql upgrades there. We'll see what they say. =20 > As soon as the 72 hours on this news announcement are done, I'm going t= o > 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. >=20 > 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. >=20 > That is of course me assuming that you have a way to issue 'REPAIR TABL= E > ...', because that's a critical MySQL command for the DBA/user to know > in managing their data. I'd think KDE would have mysql upgrade methods documented, if they're=20 going to be using the software. But there's a lot of stuff I'd have=20 thought, before the kde4 upgrade mess, that I'm considerably more cynical= =20 about now... --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman