summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAymeric Augustin <aymeric.augustin@m4x.org>2011-11-20 10:31:22 +0000
committerAymeric Augustin <aymeric.augustin@m4x.org>2011-11-20 10:31:22 +0000
commit1240c8332db9ac68be0c9b0d17c8cc8b3a68cc01 (patch)
tree70c8e9e5df92ec880ee09461026ebe090d5219f2 /docs
parent7075e932565d3a28d53ff014f0e33ce46df53496 (diff)
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
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/databases.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index ae47667628..b914a68945 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -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.