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

Fixed #17267 -- Clarified the description of MyISAM's lack of support for foreign keys. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@17120 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Aymeric Augustin 2011-11-20 10:31:22 +00:00
parent 7075e93256
commit 1240c8332d
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/ref/databases.txt
View File

@ -135,9 +135,10 @@ Storage engines
MySQL has several `storage engines`_ (previously called table types). You can
change the default storage engine in the server configuration.
The default engine is MyISAM_ [#]_. The main drawback of MyISAM is that it
doesn't currently support transactions or foreign keys. On the plus side, it's
currently the only engine that supports full-text indexing and searching.
The default engine is MyISAM_ [#]_. The main drawbacks of MyISAM are that it
doesn't currently support transactions or enforce foreign keys constraints. On
the plus side, it's currently the only engine that supports full-text indexing
and searching.
The InnoDB_ engine is fully transactional and supports foreign key references
and is probably the best choice at this point in time.