From 3f1b20841af48f444e23d1ac8ee7f75738a6dd9e Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Fri, 1 Nov 2013 10:59:16 +0100 Subject: [PATCH] [1.6.x] Fixed #21364 -- Specified InnoDB full-text support from MySQL 5.6.4 on Thanks thevlad at gmail.com for the report. Backport of 89116cf24a from master. --- docs/ref/databases.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 960e7b88023..3d7b347d0cc 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -213,8 +213,8 @@ in the server configuration. Until MySQL 5.5.4, the default engine was MyISAM_ [#]_. The main drawbacks of MyISAM are that it doesn't support transactions or enforce foreign-key -constraints. On the plus side, it's currently the only engine that supports -full-text indexing and searching. +constraints. On the plus side, it was the only engine that supported full-text +indexing and searching until MySQL 5.6.4. Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully transactional and supports foreign key references. It's probably the best