Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #18256 - Added a potential pitfall when upgrading to MySQL 5.5.5

  • Loading branch information...
commit c870cb48cd0ec4b5dfdc5df95e6f0b5f5f8a738b 1 parent f8c3acc
Tim Graham authored October 12, 2012

Showing 1 changed file with 10 additions and 0 deletions. Show diff stats Hide diff stats

  1. 10  docs/ref/databases.txt
10  docs/ref/databases.txt
@@ -158,6 +158,16 @@ Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully
158 158
 transactional and supports foreign key references. It's probably the best
159 159
 choice at this point.
160 160
 
  161
+If you upgrade an existing project to MySQL 5.5.5 and subsequently add some
  162
+tables, ensure that your tables are using the same storage engine (i.e. MyISAM
  163
+vs. InnoDB). Specifically, if tables that have a ``ForeignKey`` between them
  164
+use different storage engines, you may see an error like the following when
  165
+running ``syncdb``::
  166
+
  167
+    _mysql_exceptions.OperationalError: (
  168
+        1005, "Can't create table '\\db_name\\.#sql-4a8_ab' (errno: 150)"
  169
+    )
  170
+
161 171
 .. versionchanged:: 1.4
162 172
 
163 173
 In previous versions of Django, fixtures with forward references (i.e.

0 notes on commit c870cb4

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