#7551: GenericForeignKey fails if initialized to None during model init
-----------------------------------+----------------------------------------
Reporter: SamBull | Owner:
Status: new | Milestone: post-1.0
Component: Contrib apps | Version: SVN
Resolution: | Keywords: contenttypes
genericforeignkey
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-----------------------------------+----------------------------------------
Comment (by SamBull):
I've tried to provide a better patch.
I agree that this is an unusual situation, but it can cause hard to debug
errors. The problem is that you might be passing in an object via the
model's constructor and not know if it's None or not.
Null GFK fields are allowed, so passing in a value that might be None
should be allowed as well.
I do agree that this may not be needed for 1.0, but I wanted to highlight
the problems this bug causes.
--
Ticket URL: <http://code.djangoproject.com/ticket/7551#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
