Navigation Menu

Skip to content

Commit

Permalink
Merge pull request #8 from hiroyuki-sato/convert_to_markdown
Browse files Browse the repository at this point in the history
Convert textile to markdown

GitHub #8 

Patch by @hiroyuki-sato . Thanks!!!
  • Loading branch information
kenhys committed Feb 9, 2016
2 parents eadc64e + 27be265 commit a6793da
Show file tree
Hide file tree
Showing 158 changed files with 5,066 additions and 4,341 deletions.
14 changes: 14 additions & 0 deletions en/_posts/2011-10-29-release.md
@@ -0,0 +1,14 @@
---
layout: post.en
title: Groonga storage engine 1.0.1 has been released
---
## Groonga storage engine 1.0.1 has been released

Groonga storage engine has been released.

* [Changes of groonga storage engine in 1.0.1](http://mroonga.org/docs/news.html#release-1-0-1)

This release improves geo search feature and dynamic index modification
in storage mode. Now groonga storage engine works faster rather than
MyISAM. We still have an improvement plan, geo search will be improved
in the next release too.
11 changes: 0 additions & 11 deletions en/_posts/2011-10-29-release.textile

This file was deleted.

14 changes: 14 additions & 0 deletions en/_posts/2011-11-05-osc2011-db.md
@@ -0,0 +1,14 @@
---
layout: post.en
title: Groonga storage engine introduction at OSC2011 DB at Japan
---
## Groonga storage engine introduction at OSC2011 DB at Japan

We had presentation about [groonga storage engine
introduction](/publication/presentation/osc2011-db-groonga-storage-engine.pdf)
(PDF) at [OSSDB
MySQL](https://www.ospn.jp/osc2011.db/modules/eguide/event.php?eid=15)
in [OSC2011 DB at Japan](https://www.ospn.jp/osc2011.db/) . The PDF
includes a few benchmarks for introducing groonga storage engine's
performance characteristic. Please check it for learning groonga storage
engine's performance characteristic.
7 changes: 0 additions & 7 deletions en/_posts/2011-11-05-osc2011-db.textile

This file was deleted.

19 changes: 19 additions & 0 deletions en/_posts/2011-12-29-release.md
@@ -0,0 +1,19 @@
---
layout: post.en
title: Mroonga 1.11 has been released
---
## Mroonga 1.11 has been released

[Mroonga 1.11](/docs/news.html#release-1-11) has been released!

How to install:: [Install](/docs/install.html)

### CHARSET support

Mroonga 1.10 or ealier only supports UTF-8 but mroonga 1.11 or later
supports no UTF-8 encodings, Latin-1, CP932 and so on, are supported.

### Changes

Changes since 1.10: [Release 1.11 -
2011/12/29](/docs/news.html#release-1-11)
17 changes: 0 additions & 17 deletions en/_posts/2011-12-29-release.textile

This file was deleted.

84 changes: 84 additions & 0 deletions en/_posts/2012-01-29-release.md
@@ -0,0 +1,84 @@
---
layout: post.en
title: Mroonga 1.20 has been released
---
## Mroonga 1.20 has been released

[Mroonga 1.20](/docs/news.html#release-1-20) has been released!

How to install:: [Install](/docs/install.html)

### CAUTION![]()!

This release requires database dump and restore for upgrading. Here are
upgrade sequence.

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

1. Storage engine name is changed to "mroonga" from "groonga".
2. Groonga's native time data value are used for DATE, DATETIME and
TIMESTAMP type values.

We need to modify dumped database to change "ENGINE=groonga" in "CREATE
TABLE" SQL. Here are upgrade sequence.

We dump a database that uses mroonga:

% mysqldump MY_MROONGA_DATABASE > database-groonga.dump

We convert storage engine in dump file:

% sed -e 's/^) ENGINE=groonga/) ENGINE=mroonga/' database-groonga.dump > database-mroonga.dump

We confirm that ENGINE=groonga only in CREATE TABLE is replaced with
ENGINE=mroonga. We need to check `@ ... `@ line includes CREATE TABLE.
If the line includes CREATE TABLE, the hunk will be a change for CREATE
TABLE:

% diff -up database-groonga.dump database-mroonga.dump
--- database-groonga.dump 2012-01-29 16:53:20.732624670 +0900
+++ database-mroonga.dump 2012-01-29 16:54:47.608420981 +0900
@@ -29,7 +29,7 @@ CREATE TABLE `diaries` (
PRIMARY KEY (`id`),
FULLTEXT KEY `title_index` (`title`),
FULLTEXT KEY `body_index` (`body`)
-) ENGINE=groonga DEFAULT CHARSET=utf8;
+) ENGINE=mroonga DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;

--

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

### Changes

Changes since 1.11: [Release 1.20 -
2012/01/29](/docs/news.html#release-1-20)
90 changes: 0 additions & 90 deletions en/_posts/2012-01-29-release.textile

This file was deleted.

58 changes: 58 additions & 0 deletions en/_posts/2012-02-29-release.md
@@ -0,0 +1,58 @@
---
layout: post.en
title: Mroonga 2.00 has been released
---
## Mroonga 2.00 has been released

[Mroonga 2.00](/docs/news.html#release-2-00) has been released!

How to install:: [Install](/docs/install.html)

### CAUTION![]()!

This release requires database dump and restore for upgrading. Here are
upgrade sequence.

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.

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.

### Changes

Changes since 1.20: [Release 2.00 -
2012/02/29](/docs/news.html#release-2-00)
65 changes: 0 additions & 65 deletions en/_posts/2012-02-29-release.textile

This file was deleted.

9 changes: 9 additions & 0 deletions en/_posts/2012-03-27-logo.md
@@ -0,0 +1,9 @@
---
layout: post.en
title: The new logos have been released
---
## The new logos have been released

The mroonga project has been released [the new logos](/logo/) . They are
licensed under the CC-BY 3.0. If you are a mroonga user, please use them
and spread mroonga to the world! :-)

0 comments on commit a6793da

Please sign in to comment.