Opened 8 years ago
Closed 8 years ago
#28141 closed Uncategorized (invalid)
When have null=True inside ForeignKey, Django don't to do CASCADE Operation even passing on_delete=models.CASCADE. [using PostgreSQL]
Reported by: | mateuspadua | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.10 |
Severity: | Normal | Keywords: | ForeignKey null True PostgreSQL |
Cc: | mateuspaduaweb@… | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Example:
from cms.models import Page class OfferingPlugin(models.Model): title = models.CharField(max_length=50) subtitle = models.CharField(max_length=140) link_copy = models.CharField(max_length=20) link_address = models.ForeignKey(Page, blank=True, null=True, on_delete=models.CASCADE) ** -> dont work because has null=True** .... page = Page.objecs.first()
If I to try delete a Page instance, for example page.delete() the error bellow will occur:
.....
IntegrityError: insert or update on table "offering_offeringplugin" violates foreign key constraint "offering_offering_cmsplugin_ptr_id_9a9e9998_fk_cms_cmsplugin_id"
DETAIL: Key (id)=(10) is still referenced from table "offering_offeringplugin".
Change History (6)
comment:1 by , 8 years ago
Description: | modified (diff) |
---|
comment:2 by , 8 years ago
Description: | modified (diff) |
---|
comment:3 by , 8 years ago
Description: | modified (diff) |
---|
comment:4 by , 8 years ago
comment:5 by , 8 years ago
Thanks for replay:
I did more tests and i figure out that my constraint was without the options Deferrable and Deferred assigned, because my current DB PostgreSQL was migrate from MySQL. Then I assigned this options manually on DB and worked.
More information about this options on the link bellow:
http://stackoverflow.com/questions/16323236/deferrable-check-constraint-in-postgresql
I hope this can help.
comment:6 by , 8 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Could you please provide code to reproduce the issue (a sample project, for example) that doesn't involve a third-party project (django-cms in this case) so we can rule out a bug in that package?