"Fossies" - the Fresh Open Source Software Archive

Member "mroonga-12.04/doc/source/news/2.x.rst" (6 Jun 2022, 16926 Bytes) of package /linux/misc/mroonga-12.04.tar.gz:


As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field.

News - 2.x

Release 2.10 - 2012/12/29

Improvements

Fixes

Thanks

Release 2.09 - 2012/11/29

Caution

This release has backward incompatible changes against TIMESTAMP value and primary indexed char(N).

TIMESTAMP value is changed to store as UTC timezone. If you have any table that uses TIMESTAMP column with no UTC timezone, please recreate (dump and restore) database.

If you have any table that uses char(N) as primary key, please recreate index.

Here is a procedure how to recreate database or recreate index.

Dump a database that uses mroonga:

% mysqldump MY_MROONGA_DATABASE > database-mroonga.dump

Restore a database by modified dump file:

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

Recreate a index:

mysql> ALTER TABLE table_name DROP PRIMARY KEY;
mysql> ALTER TABLE table_name ADD PRIMARY KEY(column_name);

Improvements

Fixes

Thanks

Release 2.08 - 2012/10/29

Caution

This release has a backward incompatible change against multiple column index. If you have any tables that uses any multiple comlumn indexes against VARCHAR or CHAR, please recreate those indexes by ALTER TABLE DISABLE KEYS and ALTER TABLE ENBALE KEYS:

mysql> ALTER TABLE table_name DISABLE KEYS;
mysql> ALTER TABLE table_name ENABLE KEYS;

Improvements

Fixes

Thanks

Release 2.07 - 2012/09/29

Improvements

Fixes

Thanks

Release 2.06 - 2012/08/29

Caution

This release has a backward compatibility about a database. But this release depends on new functionality introduced at groonga 2.0.6. Note that you must use mroonga 2.06 with groonga 2.0.6.

Improvements

Fixes

Thanks

Release 2.05 - 2012/07/29

Caution

This release has a backward incompatible change against SET column and ENUM. If you use SET column or ENUM that has the number of elements < 256 in /tutorial/storage, please recreate (dump and restore) database.

Here is upgrade sequence.

Dump a database that uses mroonga:

% mysqldump MY_MROONGA_DATABASE > database-mroonga.dump

Drop the existing database:

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

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

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

Recreate a database:

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

Restore a database by modified dump file:

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

Now, we can use mroonga 2.05.

Improvements

Release 2.04 - 2012/06/29

Improvements

Fixes

Thanks

Release 2.03 - 2012/05/29

Caution

This release has a backward incompatible change against multiple column index. If you have any tables that uses /tutorial/storage and any multiple comlumn indexes, please recreate those indexes by ALTER TABLE DISABLE KEYS and ALTER TABLE ENBALE KEYS:

mysql> ALTER TABLE table_name DISABLE KEYS;
mysql> ALTER TABLE table_name ENABLE KEYS;

Improvements

Fixes

Thanks

Release 2.02 - 2012/04/29

Caution

The package sign key is changed since this release. Import the new package sign key before updating groogna packages.

Debian/Ubuntu:

% sudo apt-get update
% sudo apt-get -y --allow-unauthenticated install groonga-keyring

CentOS/Fedora:

% sudo yum update
% sudo yum install --nogpgcheck -y groonga-repository

Caution

This release breaks a backward compatibility for ENUM type. If you have ENUM type and it has 256 or more values, you need to dump your table before upgrade and restore your table after upgrade.

Caution

This release breaks a backward compatibility for SET type. If you have SET type and it has 32 or more values, you need to dump your table before upgrade and restore your table after upgrade.

Improvements

Fixes

Thanks

Release 2.01 - 2012/03/29

Improvements

Fixes

Thanks

Release 2.00 - 2012/02/29

Caution

This release breaks backward compatibility. We need to dump and restore our database for upgrading.

In this release, mroonga has two changes that requires database recreation:

  1. Supported all characters for database, table and column names.
  2. Groonga's native time data type is used for YEAR type in MySQL.

Here are upgrade sequence.

We dump a database that uses mroonga:

% mysqldump MY_MROONGA_DATABASE > database-mroonga.dump

We drop the existing database:

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

We upgrade to "mroonga" storage engine. We will 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:

% sudo yum remove -y mysql-mroonga
% 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 a MySQL's system table.

We recreate a database:

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

We restore a database by modified dump file:

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

Now, we can use mroonga 2.00.

Improvements

Fixes

Thanks