#33629: Errors in PostgreSQL instruc on delete
-------------------------------------+-------------------------------------
Reporter: wrcarrizo | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => invalid
* component: Uncategorized => Database layer (models, ORM)
* type: Uncategorized => Bug
Comment:
[https://docs.djangoproject.com/en/4.0/ref/models/fields/#django.db.models.CASCADE
As documented], "Django emulates the behavior of the SQL constraint ON
DELETE CASCADE and also deletes the object containing the ForeignKey."
(Django doesn't create an `ON DELETE CASCADE` constraint.)
I'm not sure what you mean by "and does not generate on UPDATE." If you
believe there's a bug in Django, please give a more detailed explanation.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/33629#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018010866160-71ea830e-cf87-4538-9f85-1d48f2cfd30f-000000%40eu-central-1.amazonses.com.
