diff options
| author | Tim Graham <timograham@gmail.com> | 2012-10-12 06:37:35 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-10-12 19:17:00 -0400 |
| commit | c870cb48cd0ec4b5dfdc5df95e6f0b5f5f8a738b (patch) | |
| tree | 663a5fcc0d0d3e99c8651ef915f4234d0abb3f0e /docs/ref | |
| parent | f8c3acc8074988eed88667e58255abab1b093119 (diff) | |
Fixed #18256 - Added a potential pitfall when upgrading to MySQL 5.5.5
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/databases.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 3e256e9d9e..3a52f838e7 100644 --- a/docs/ref/databases.txt +++ b/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. |