On 11 joulu, 17:56, Anssi Kääriäinen <[email protected]> wrote: > Would a model._meta.get_default_columns() work for you? While this > would still be internal API, it would be hopefully less likely to > change in ways that require extensive rewrites to 3rd party apps.
First, the ._meta.get_default_columns() I proposed above doesn't actually make sense - the get_default_columns() does mostly things which belong to compiler, not to ._meta. Second, I have created a patch which should allow your work to continue working in master. See https://github.com/akaariai/django/commit/94c417d2a29a0f72b26019fc38ef400420097aa4 - the idea is to change get_fields_with_model() so that it doesn't return different values for proxy models compared to concrete models. I think this is a good solution overall, though this change is somewhat scary - get_fields_with_model is used in many places of the ORM... Third, I think it is a good idea to add more abstraction between the ORM and the Model/Fields layer. So, in this way I do support the idea of using proxy models for single table inheritance. On the other hand it should not be surprising if in the future "different fields than parents" proxy models will break again - it is almost the definition of proxy model that it has the same fields than its parent. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
