On 25 September 2012 17:45, Alex Ogier <alex.og...@gmail.com> wrote: > There's a big thing you cannot do without grouping models: you can't have > an abstract base class relate to another abstract base class. Django's > foreign key mechanism doesn't know how to relate to a to-be-instantiated > concrete class. >
Not entirely true, the foreign key can use a string 'app.Model', we've used this mechanism quite extensively in Oscar (an e-commerce) platform to allow overriding or extending of any model without having to change the code for other models. That said, we have to do some quite ugly tricks to get this working properly. I'm intrigued by this ModelFactory approach because it can potentially remove some of our hacks, but I'm not overly keen on adopting an new idiom that isn't widely accepted as a good approach. So I'm following this discussion with interest. - Andy Ingram -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
