#16119: ForeignKey.on_delete emulated only
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
mischiew@… | Status: closed
Type: New | Component: Database layer
feature | (models, ORM)
Milestone: | Severity: Normal
Version: 1.3 | Keywords: foreign key, on
Resolution: invalid | delete
Triage Stage: | Has patch: 0
Unreviewed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by kmtracey):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
This sounds like a dupe of #7539, which was implemented for 1.3, see:
https://docs.djangoproject.com/en/1.3/releases/1.3/#configurable-delete-
cascade and
https://docs.djangoproject.com/en/1.3/ref/models/fields/#django.db.models.ForeignKey.on_delete
Yet the version here has been set to 1.3, which is a bit confusing. If
there is something lacking in the 1.3-implemented support please spell it
out more clearly. RESTRICT corresponds to PROTECT in the Django
implementation; if you do not want Django to emulate cascade then on the
Django side you specify DO_NOTHING and ensure that the DB is set up
properly to do the cascade itself.
--
Ticket URL: <https://code.djangoproject.com/ticket/16119#comment:1>
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.
