I think the overall recommended design practice in this case is to favor composition over inheritance. In our application, we have an application specific user entity that has a db.UserProperty(). Works pretty well and is super easy to implement. An example can be found here: http://code.google.com/appengine/docs/users/userobjects.html
-Mahmoud On Oct 14, 11:15 am, Alex Vartan <[EMAIL PROTECTED]> wrote: > Apologies if this is a simple question, I'm still a python / GAE > novice. Is it possible to subclass the User class? I have just a > couple of extra properties and I'd like to store with User and rather > not create a duplicated UserOfMyApp class that includes a user as a > property if I can just subclass the User class itself. > > What's the best solution if I just want to store a reference to > another model and a few integerproperties with a user? > > Regards, > Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
