Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

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

  • Loading branch information...
commit c870cb48cd0ec4b5dfdc5df95e6f0b5f5f8a738b 1 parent f8c3acc
@timgraham timgraham authored
Showing with 10 additions and 0 deletions.
  1. +10 −0 docs/ref/databases.txt
View
10 docs/ref/databases.txt
@@ -158,6 +158,16 @@ Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully
transactional and supports foreign key references. It's probably the best
choice at this point.
+If you upgrade an existing project to MySQL 5.5.5 and subsequently add some
+tables, ensure that your tables are using the same storage engine (i.e. MyISAM
+vs. InnoDB). Specifically, if tables that have a ``ForeignKey`` between them
+use different storage engines, you may see an error like the following when
+running ``syncdb``::
+
+ _mysql_exceptions.OperationalError: (
+ 1005, "Can't create table '\\db_name\\.#sql-4a8_ab' (errno: 150)"
+ )
+
.. versionchanged:: 1.4
In previous versions of Django, fixtures with forward references (i.e.
Please sign in to comment.
Something went wrong with that request. Please try again.