Changes between Version 1 and Version 2 of Ticket #22778, comment 8


Ignore:
Timestamp:
Jun 10, 2014, 11:03:52 AM (10 years ago)
Author:
jorgecarleitao

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #22778, comment 8

    v1 v2  
    55As far as I can tell, the PR still requires:
    66
    7 1. to address Meta subclassing yet: i.e. what happens when the Model is subclassed? At the moment it seems the `default_related_name` is inherited, which can cause a clash; see [1].
     71. to address Meta subclassing: i.e. what happens when the Model is subclassed? At the moment it seems the `default_related_name` is inherited, which can cause a clash; see [1].
    88
    992. tests: it passes all tests means it is compatible with current Django functionality, which is great; however, we must ensure it is also compatible with what we want to achieve with it, namely, that if we add a `default_related_name` to `Meta`, the relations without `related_name` get the default one, while others don't. We may also want to test subclassing.
Back to Top