Hoping someone might help me with a somewhat OT question. I developed an object model for a GAE/J application that worked fairly well for awhile (and it was fun watching how easy it was to persist the instances to the datastore). But now I need to extend the model. Each "Campaign" instance I use needs to be related (many-to-many) with new "FundingOrganization" instances. I'm suspecting there may be other similar extensions I'll need to make to the model after the fact (additional categories associated with the Campaign).
I can think of approaches to refactoring the application that include changing the Campaign class to know about FundingOrganization (http:// code.google.com/appengine/docs/java/datastore/ relationships.html#Unowned_Relationships), but I'd prefer to keep the entities pretty simple without adding a property for each new category that comes up. Can someone point this rookie to intro material/URLs for building and refactoring designs that lend themselves to these type of changes? I'm looking for info on adaptable design, especially when you're using a datastore and not using a RDBMS, junction tables, etc. thanks, Hans --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en -~----------~----~----~----~------~----~------~--~---
