public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: News item: MySQL 5.1 bump
Date: Tue, 16 Feb 2010 04:33:20 +0000	[thread overview]
Message-ID: <robbat2-20100216T042654-723126279Z@orbis-terrarum.net> (raw)
In-Reply-To: <pan.2010.02.16.04.20.28@cox.net>

On Tue, Feb 16, 2010 at 04:20:27AM +0000, Duncan wrote:
> """
> Note that existing databases will need converted as well,
> again including those upgrading from 5.0 to 5.1.
> Details can be found in the official upgrade docs at:
> http://dev.mysql.com/doc/refman/5.1/en/upgrade.html
> """
_may_ need to be converted, not _will_. 

> If you wish to put the unofficial upgrade recommendation in too, that 
> would be fine.
That would encourage users not to read the above document.

> Hopefully that'll cover us users that don't particularly care about 
> databases, we just want our kde to work... and it'll continue to do so. 
> =:^)  (IOW, are there any particularly different procedures for upgrading 
> databases in user's $HOME dirs? 
- If you're using embedded MySQL (Amarok), you're going to be on your
  own.
- 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).

> 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.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85



  reply	other threads:[~2010-02-16  4:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 21:21 [gentoo-dev] News item: MySQL 5.1 bump Robin H. Johnson
2010-02-15 21:32 ` Samuli Suominen
2010-02-15 21:41   ` Robin H. Johnson
2010-02-16  0:08     ` Thilo Bangert
2010-02-15 21:51 ` [gentoo-dev] " Nikos Chantziaras
2010-02-15 22:12   ` Robin H. Johnson
2010-02-16 10:27     ` Nikos Chantziaras
2010-02-15 22:03 ` [gentoo-dev] " Ulrich Mueller
2010-02-15 22:06 ` Dawid Węgliński
2010-02-15 22:15   ` Robin H. Johnson
2010-02-15 22:54     ` Dawid Węgliński
2010-02-16  0:14 ` Robin H. Johnson
2010-02-16  4:20   ` [gentoo-dev] " Duncan
2010-02-16  4:33     ` Robin H. Johnson [this message]
2010-02-16  6:11       ` Duncan
2010-02-16  6:26         ` Robin H. Johnson
2010-02-16 10:14           ` Duncan
2010-02-16 10:34             ` Duncan
2010-02-16 14:37           ` Petteri Räty
2010-02-16 18:48             ` Joshua Saddler
2010-02-16 19:20               ` Robin H. Johnson
2010-02-16 19:48                 ` Joshua Saddler
2010-02-21  2:23 ` [gentoo-dev] " Robin H. Johnson
2010-02-21 12:01   ` Richard Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=robbat2-20100216T042654-723126279Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox