#3851: unique_together with an empty value for a ForeignKey
----------------------------------------------------+-----------------------
Reporter: rezzrovv <[EMAIL PROTECTED]> | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: fixed | Keywords:
unique_together
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------------+-----------------------
Changes (by kmtracey):
* status: new => closed
* resolution: => fixed
Comment:
Calling this fixed because the manipulator code involved is gone, and I
know null !ForeignKey values with current forms & unique_together do work
OK.
--
Ticket URL: <http://code.djangoproject.com/ticket/3851#comment:5>
Django <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
-~----------~----~----~----~------~----~------~--~---
