Hi all, looking for some guidance here... I often find myself using inheritance in such a way that it also indicates state. For example, we might have a PlacedOrder class that will go through an approval process before it becomes the more specialized ApprovedOrder class. The ApprovedOrder class is still a PlacedOrder and maintains all the same attributes while adding a few.
The problem comes when classes are immutable - you have to create the new class, copy all the attributes, then destroy the old - thats a drag. I would much prefer to just change the class type then fill in the outstanding attributes. Polymodel, to me, seems to be mutable in that way and I just wanted to get some advice and opinions about it before I charge ahead... Thanks in advance, 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.
