#33629 closed Bug (invalid)
Errors in PostgreSQL instruc on delete
| Reported by: | wrcarrizo | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 3.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Django does not correctly generate postgreSQL onDelete Cascade, and does not generate on UPDATE
Change History (1)
comment:1 by , 3 years ago
| Component: | Uncategorized → Database layer (models, ORM) |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
| Type: | Uncategorized → Bug |
Version 0, edited 3 years ago by (next)
Note:
See TracTickets
for help on using tickets.
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 CASCADEconstraint.)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.