Hey Rein, With some poking around you could probably devise a way to change the class attribute. I remember looking into do this, but decided it would be easier to simply create my own implementation. PolyModel is not particularly complicated, but you'll probably do a lot of work for something solvable in other ways. Another part of the reason I went with a roll-your-own approach is that I wanted Expando-like (dynamic properties) features anyway.
Robert On Mon, Nov 29, 2010 at 18:03, Rein Petersen <[email protected]> wrote: > Robert, > Thanks for saving me a bunch of time in discovering that Polymodel class > field is unchangeable - I will take your word for it because I am too lazy > to do the testing ;) > I like your idea for using Expando - I will probably go that route unless my > Expando class has to inherit from a PolyModel class - then I am back to > square one and will have to dig up the source on PolyModel and discover why > the class field is unchangeable and how I might overcome that. > Thanks again > 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. > -- 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.
