It turns out that after listening to advice and doing some more reading that I have corrections to make and an admission that what I have suggestied is probably a bad idea (although there is a strong likelihood I will do it anyway). I found in Python documentation that an object's type may not be changed although what I am proposing is changing a class property that will change the Polymodel object's type at serialization, not during runtime.
Digging into Javascript on the subject suggests that it is a dynamically-typed language in that you may bound and unbound a variable from one object of one type to another object of another type. I suppose you can call that dynamic typing but the way I have proposed doing it (which works for me in the latest generation of browsers), is undocumented and clearly an internal variable not intended for general usage. Searching around OOP information hasn't yielded any definitive information on the subject so I can't really decide if this is probably just a risky practice to achieve an end or if it is unwise and unrecommended as well. The correction: my subject line didn't really describe the subject well... of course Polymodels are mutable - of course you can change it's attributes. Rather I would have preferred the subject line to have been Polymodel class type - mutable? I just want to end saying that if you are reading this post - please don't think that I am endorsing the use of javascript __proto__ to change a type, nor the class property of the Polymodel to change type - it is very likely a bad idea (even though I am going to do it anyway). -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
