p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #21364 -- Specified InnoDB full-text support from MySQL 5.6.4 on 

Thanks thevlad at gmail.com for the report.
This commit is contained in:
Claude Paroz 2013-11-01 10:59:16 +01:00
parent 67c6c1a7cb
commit 89116cf24a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/ref/databases.txt
View File

@ -209,8 +209,8 @@ in the server configuration.
Until MySQL 5.5.4, the default engine was MyISAM_ [#]_. The main drawbacks of 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 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 constraints. On the plus side, it was the only engine that supported full-text
full-text indexing and searching. indexing and searching until MySQL 5.6.4.
Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully 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 transactional and supports foreign key references. It's probably the best