Look here:

MySQL 5.6 リファレンスマニュアル (含むMySQL Cluster 7.3-7.4マニュアル)
 http://dev.mysql.com/doc/refman/5.6/ja/index.html
MySQL Enterprise Monitor 3.0.18 マニュアル
 http://dev.mysql.com/doc/mysql-monitor/3.0/ja/index.html
MySQL Enterprise Backup ユーザーズガイド (バージョン 3.11.1)
 http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/ja/index.html

If you cannot read this, it's because your Japanese isn't any better than mine. :-)

Jokes aside, as of June 4, 2015, some of the MySQL documentation is available in Japanese now. The biggest book that was translated is the MySQL 5.6 Manual, thousands of pages. The other books, …

Ashisuto greatly expands support services for Enterprise users of MySQL & MariaDB open source database software

So, this is exciting news and something that my colleague Daniel Saito had been working on for years: enterprise-ready, 24/365 Japanese support for the MySQL and MariaDB databases!

read more

Last week, I wrote about an experimental video program that I am coordinating for Mozilla.

I’ve now posted a more complete overview of the program, along with a draft guide for the program testers and an early FAQ on the program.

Helping us in our early stages are the following good and brave souls:

• Alina Mierlus, Free Software/Open Source advocate and a driver of Mozilla.ro
• …

I have seen a few people now ask about using MySQL's FULLTEXT indexing with asian languages such as Chinese, Japanese and Korean (herein referred to as CJK.), however, there doesn't seem to be a good centralised article that covers it.

The information is out there, I just don't think it has been well presented yet.

As I have recently done a bunch of research on this topic for a customer, I figured it might be a good opportunity to make my debut in the MySQL blogosphere.

So here we go...

I'll open by saying that attempting to use FULLTEXT with CJK text in MySQL 5.0 will be unsuccessful.

From the CJK FAQ in the MySQL manual:

"For FULLTEXT searches, we need to know where words begin and end. With Western languages, this is rarely a problem because most (if not all) of these use an easy-to-identify word boundary — the space character. However, this is not …