#2720: Wrong syntax generated for foreign keys under MySQL/InnoDB 5.0.22
--------------------------------+-------------------------------------------
 Reporter:  anonymous           |        Owner:  adrian
     Type:  defect              |       Status:  new   
 Priority:  high                |    Milestone:        
Component:  Database wrapper    |      Version:        
 Severity:  normal              |   Resolution:        
 Keywords:  innodb foreign key  |  
--------------------------------+-------------------------------------------
Comment (by [EMAIL PROTECTED]):

 Would that be evident in "manage.py sqlindexes <appname>"?  I'm not seeing
 any constraints added there.
 
 When I look at the SQL output by "manage.py sql <appname>", I see the
 first syntax used above; when I drop the table and recreate it with that
 foreign-key syntax, the table is created with no foreign key (it's
 consistent for a given table - if it fails once, it always fails).
 
 When I drop the table and recreate it with the second syntax used above,
 it always succeeds.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2720>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---

Reply via email to