#10010: ManyToMany programming error
---------------------------------------------------+------------------------
Reporter: rmaciejc...@nglogic.com | Owner: nobody
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by ramiro):
Replying to [comment:5 rmaciejc...@nglogic.com]:
> Yes, it's done intentionally, since both these fields have been set in
my database as primary key (they are unique together).
But it a unsupported configuration, see
http://docs.djangoproject.com/en/dev/ref/models/fields/#primary-key
It seems there isn't a check for this in
`django/core/management/validation.py`.
--
Ticket URL: <http://code.djangoproject.com/ticket/10010#comment:6>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
