#2111: Admin site can't deal with broken ForeignKeys
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: Admin
interface
Version: | Resolution: wontfix
Keywords: admin, foreignkey | Stage: Design
decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------------+----------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
I think this is outside the scope of the admin interface. Repairing
database integrity is a bit database-specific and something that has to be
done at another level, usually with special tools. The admin interface
assumes the persistent store is going to be well-behaved underneath it and
adding special checks in for all the (very rare) cases where that might
not happen will just complicate the code.
--
Ticket URL: <http://code.djangoproject.com/ticket/2111#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
