#2415: AutomaticManipulator with foreign keys and unique_together fails
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: reopened | Component: Core framework
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 1 | Needs_better_patch: 0
--------------------------------+-------------------------------------------
Changes (by Gary Wilson <[EMAIL PROTECTED]>):
* status: closed => reopened
* resolution: wontfix =>
* needs_tests: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Even though this probably won't get fixed for manipulators (unless someone
really wants it and submits a patch, in which case we will gladly accept),
we do need to make sure that the bug doesn't also exist in newforms. At
the very least, we should make a test for this using newforms to be
assured it has been fixed.
So as a general rule, tickets that are requesting new features for
Manipulators (like #1679) can be closed as wontfix, but tickets that are
bugs should be left open to make certain that the same problem doesn't
exist in newforms.
--
Ticket URL: <http://code.djangoproject.com/ticket/2415#comment:5>
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
-~----------~----~----~----~------~----~------~--~---
