test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.4.X] Fixed #18256 - Added a potential pitfall when upgrading to MySQL 5.5.5 

Backport of c870cb48cd from master
This commit is contained in:
Tim Graham 2012-10-12 06:37:35 -04:00
parent 8139a7990a
commit e2dea54efe
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/ref/databases.txt
View File

@ -165,6 +165,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.