Changes between Initial Version and Version 1 of Ticket #23076, comment 9


Ignore:
Timestamp:
Oct 6, 2015, 7:16:56 PM (9 years ago)
Author:
James Murty

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #23076, comment 9

    initial v1  
    33The root cause of this issue is that Django's deletion collector does not include M2M reverse references to '''proxy''' parents/ancestors of a model when deleting it; it only finds these relationships for '''concrete''' parent models. This means that deleting a proxy-based model object with extant M2M relationships targeting a proxy parent will fail with integrity errors, if you are using a database like PostgreSQL that enforces foreign key constraints.
    44
    5 I have created a Pull Requests based on the current 1.7.x branch that adds unit tests demonstrating the issue when run against PostgreSQL: https://github.com/django/django/pull/5399
     5I have created a Pull Requests based on the current master branch that adds unit tests demonstrating the issue when run against PostgreSQL: https://github.com/django/django/pull/5404
    66
    77The same issue affects 1.8, and I can follow up with a PR for that branch if it would be useful?
    … …  
    1010
    1111We could proceed with these patches, but only if the issue is considered relevant and serious enough to fix in Django core.
     12
     13[Edit: Updated PR link to latest version based on master branch]
Back to Top