Well one example is my location class, which contains countries, provinces, and cities models. Having one class allows me to write a single API that is self contained and very modular to handle any location related task.
On Tue, May 15, 2012 at 1:35 PM, Bruno Rocha <[email protected]> wrote: > I am looking in to it, and realized that there ia a better, simple and > more elegant way. > > In Django models, it is very commom to use a subclass named Meta, so I > will try to run something like. > > > class Dog(BaseModel): > self.name = Field("name") > self.guardian = Field("guardian", "reference guardian") > > class Meta: > tablename = "dog" > migrate = False > ... > > > I will try it today... > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.fittraineronline.com - Fitness Personal Trainers Online http://www.warplydesigned.com
