Author: aaugustin Date: 2011-11-20 02:31:22 -0800 (Sun, 20 Nov 2011) New Revision: 17120
Modified: django/trunk/docs/ref/databases.txt Log: Fixed #17267 -- Clarified the description of MyISAM's lack of support for foreign keys. Modified: django/trunk/docs/ref/databases.txt =================================================================== --- django/trunk/docs/ref/databases.txt 2011-11-20 10:17:12 UTC (rev 17119) +++ django/trunk/docs/ref/databases.txt 2011-11-20 10:31:22 UTC (rev 17120) @@ -135,9 +135,10 @@ 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. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
