#9525: It should be possible to disable the creation of database key
constraints
in ForeignKey Field
---------------------------------------------------+------------------------
Reporter: mohlendo | Owner: nobody
Status: closed | Milestone: post-1.0
Component: Database layer (models, ORM) | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think that if you want to do this, you should create a special field to
do so. A `ForeignKey` is traditionally understood as modelling a many-to-
one relation, not many-to-many, and that's certainly the case in Django.
Extending the meaning beyond that would confuse things a bit.
It's an interesting idea, but not really how a database models things, so
you will need to do some manual validation in your custom field to ensure
data integrity.
--
Ticket URL: <http://code.djangoproject.com/ticket/9525#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
