#2493: Error "reset"ing app with self-referencing ForeignKey
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: anonymous
Status: assigned | Component: Database wrapper
Version: SVN | Resolution:
Keywords: sprintdec01 | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Changes (by empty <[EMAIL PROTECTED]>):
* owner: empty => anonymous
* status: new => assigned
Comment:
Confirmed that it's a problem but for the reason mtredinnick stated. The
issue is that the constraint name is built up by doing a hash on the two
related table names. If the constraint name was changed manually, or
otherwise it the drop statement will be invalid. The best solution is to
use introspection as mtredinnick suggested.
Some of the odd behavior may also have been related to the #4193 issue,
but that's covered there.
--
Ticket URL: <http://code.djangoproject.com/ticket/2493#comment:7>
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
-~----------~----~----~----~------~----~------~--~---
