diff options
| author | Claude Paroz <claude@2xlibre.net> | 2013-11-01 10:59:16 +0100 |
|---|---|---|
| committer | Claude Paroz <claude@2xlibre.net> | 2013-11-01 11:02:48 +0100 |
| commit | 60ec8ae4b2165d827fbdabc287c07c95794103ec (patch) | |
| tree | ae91d9be079c005273e6cbc41d73f240d01e8d42 /docs | |
| parent | dd0c204828f58f63caa573b0a03df7665c97e6d3 (diff) | |
[1.5.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.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/databases.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 60001abcb5..15dfc40b57 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -156,8 +156,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 |