Malcolm Tredinnick wrote: > Rather than watch the "inherit from User" thread go round and round, > maybe I should give people something more concrete to think about. > > This is a follow-up to the mail I sent late on Friday. It describes the > area where we need API additions or some kind of semi-major change to > incorporate model inheritance and some developer feedback would be a > good idea. I am only talking about the API here, not the implementation > (since you will notice there is no patch attached to the email). > > Model inheritance (as I've implemented it) comes in two varieties, > differentiated by the way they store the data at the db level and by the > way you use them at the Python level. > > ----------------------- > 1. Abstract Base class > -----------------------
+1e6 Great!!! Just when I need it - I'm going through pain of maintaining four separate models with lot's of common fields. Go for it. > --------------------------- > 2. "Pythonic" Inheritance > ---------------------------- +1 even better (I'm not in any way database and/or django ORM expert so I will not comment actual implementation). -- Nebojša Đorđević - nesh Studio Quattro - Niš - SCG http://studioquattro.biz/ http://djnesh.blogspot.com/ | http://djnesh-django.blogspot.com/ | http://trac.studioquattro.biz/djangoutils/ Registered Linux User 282159 [http://counter.li.org] --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
