Skip to content
Browse files

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
  • Loading branch information...
1 parent 7075e93 commit 1240c8332db9ac68be0c9b0d17c8cc8b3a68cc01 @aaugustin aaugustin committed
Showing with 4 additions and 3 deletions.
  1. +4 −3 docs/ref/databases.txt
View
7 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.

0 comments on commit 1240c83

Please sign in to comment.
Something went wrong with that request. Please try again.