#2720: Wrong syntax generated for foreign keys under MySQL
----------------------------------+-----------------------------------------
Reporter: anonymous | Owner: adrian
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: innodb foreign key | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
----------------------------------+-----------------------------------------
Comment (by Michael Radziej <[EMAIL PROTECTED]>):
Replying to [comment:12 russellm]:
> How does this patch interact with #3390 - in particular, the test for
forward references in deserialization data? When I worked up that patch, I
was surprised that there weren't any MySQL complaints about data
consistency, but if I'm understanding this problem correctly, the
constraints may not be operating correctly on MySQL...
Hmm, our two patches conflict with each other, and I'm too tired now to
resolve the conflicts.
I got failures when I tried #3390 (without #2720) on a postgresql backend.
You can probably get similar results when you reorder your model classes
so that you only have forward references.
--
Ticket URL: <http://code.djangoproject.com/ticket/2720#comment:13>
Django Code <http://code.djangoproject.com/>
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?hl=en
-~----------~----~----~----~------~----~------~--~---
