Hello,
thanks for the reply. On Mon, Mar 12, 2012 at 03:20:10PM -0400, Shawn Milochik wrote: > First, I would avoid using the word 'list' for describing anything > in your own data, since it's a Python built-in. Maybe CodeList or > PromoList or something, if they're going to be promotion codes. Or > maybe just Promo, since a model should be a singular name, and each > instance of your model will be a single item, not actually a list. well, you're right, using "list" should misleading - thanks. > I think you can do what you want my making a class that subclasses > models.Model, then subclassing that with all of your other classes. > > As long as you don't make the base class "abstract," adding > instances to any subclass will create an instance of the base class. > > I think that answers your question, but I don't understand your > description well enough to claim that this is the best approach to > the problem you're trying to solve. umm, no, sorry, I've wrote my problem incomplete. The main problem is the PromoList is _dynamyc_ - it means all administrator on admin site should add new PromoList, without me :), so I can't derivate all subclass in code... May be this would be clear.... Thanks: a. -- I � UTF-8 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
