Navigation Menu

Skip to content

Commit

Permalink
doc: update "upgrade sequence"
Browse files Browse the repository at this point in the history
  • Loading branch information
kenhys committed Jul 27, 2012
1 parent ea4a6a9 commit ac20bff
Showing 1 changed file with 14 additions and 9 deletions.
23 changes: 14 additions & 9 deletions doc/source/news.rst
Expand Up @@ -16,40 +16,45 @@ Release 2.05 - 2012/07/29
in :doc:`/userguide/storage`, please recreate (dump and restore)
database.

Here are upgrade sequence.
Here is upgrade sequence.

We dump a database that uses mroonga::
Dump a database that uses mroonga::

% mysqldump MY_MROONGA_DATABASE > database-mroonga.dump

We drop the existing database::
Drop the existing database::

% mysql -u root -e 'DROP DATABASE MY_MROONGA_DATABASE'

We upgrade to "mroonga" storage engine. We will use
You must upgrade to "mroonga" storage engine. Use
``apt-get`` on Debian GNU/Linux or Ubuntu and ``yum`` on
CentOS or Fedora.

apt-get::

% sudo apt-get install -y mysql-server-mroonga

yum::
yum (upgrade from mroonga release prior to v2.02)::

% sudo yum remove -y mysql-mroonga
% sudo yum install -y mysql-mroonga

yum (upgrade from mroonga release v2.03 or later)::

% sudo yum install -y mysql-mroonga

.. caution::

We don't forget to run ``yum remove`` before ``yum
install``. If we forget to run ``yum remove``, we will break
Don't forget to run ``yum remove`` before ``yum
install`` if you upgrade mroonga prior to v2.02 release.
If we forget to run ``yum remove``, we will break
a MySQL's system table.

We recreate a database::
Recreate a database::

% mysql -u root -e 'CREATE DATABASE MY_MROONGA_DATABASE'

We restore a database by modified dump file::
Restore a database by modified dump file::

% mysql -u root MY_MROONGA_DATABASE < database-mroonga.dump

Expand Down

0 comments on commit ac20bff

Please sign in to comment.