#2111: Admin site can't deal with broken ForeignKeys
---------------------------------------+------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Admin interface | Version:
Severity: normal | Resolution:
Keywords: admin, foreignkey |
---------------------------------------+------------------------------------
Comment (by [EMAIL PROTECTED]):
Normally, the database protects its foreign key references when you have
declared them as such. So, this is not a common case. (How the heck did
this happen, anyway?)
I don't think this ticket has a real chance to get resolved. Their is an
assumption everywhere in the code that foreign keys match to something,
and it doesn't make sense to change this. The users mailing list might get
you a better response.
--
Ticket URL: <http://code.djangoproject.com/ticket/2111>
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
-~----------~----~----~----~------~----~------~--~---
