From 1240c8332db9ac68be0c9b0d17c8cc8b3a68cc01 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Sun, 20 Nov 2011 10:31:22 +0000 Subject: [PATCH] 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 --- docs/ref/databases.txt | 7 ++++--- 1 file 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.