#5660: inconsistent behavior of explicit primary_key and ManyToManyField
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Component: Uncategorized
Version: SVN | Resolution: invalid
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Changes (by jacob):
* status: new => closed
* resolution: => invalid
Comment:
You should never be able to add objects to an M2M if either object isn't
saved yet. The only reason this works at all with the {{{CharField}}} is
that {{{id}}} gets set to "" (the empty string) by default. You always
need to {{{save()}}} before added related objects.
--
Ticket URL: <http://code.djangoproject.com/ticket/5660#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
