Thanks Jeff, You're right - the way you have described is the way I should do it. But something bothers me about not being able to model relationships and state using inheritance. When I think about the problem domain, I really do want to model it the way I have described. I have achieved it on the client, in javascript, using __proto__ (you can hear the gasps of disgust) and it works great although undocumented and not permitted, in general, for that reason.
When I was looking at the composition of the polymodel, it became clear that I could probably manipulate it's 'class' field to change it's type (at serialization to the db), without actually changing the type (in my case python). Afterwards, the next deserialization results in the new type. I know it breaks the rules but I actually haven't seen any rules that expressly say that I cannot change an object's type - in python or javascript or in OOP - maybe I just haven't done enough reading. Rein -- 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.
