#16119: ForeignKey.on_delete emulated only
----------------------------+----------------------------------------------
Reporter: mischiew@… | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Database layer (models, ORM)
Version: 1.3 | Severity: Normal
Keywords: foreign key, | Triage Stage: Unreviewed
on delete | Easy pickings: 0
Has patch: 0 |
----------------------------+----------------------------------------------
The '''on_delete''' property of ForeignKey is only emulated by Django,
which means it is not implemented as a database definition. This has
drawbacks:
- prevents from using certain modes (especially '''RESTRICT''')
- makes it dangerous when the database is accessed by another client than
Django (why should it be restricted?)
There should be at least an option to remove the emulation and use the
normal database support when available (which is the most frequent
scenario).
On the same not, '''on_update''' would be nice to have.
Likewise for '''ManyToManyField''', support for '''on_delete''' and
'''on_update''' would be nice.
--
Ticket URL: <https://code.djangoproject.com/ticket/16119>
Django <https://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.
