I am new to the persistence model of the Google app engine and have a question on how to best model/architect the following scenario. I would really appreciate your feedback!
The Partner class can 0-n roles "implemented" (Teacher, Student, Employee, ...). Partner - Key - Name - RoleList Role abstract - Key - RoleType - RoleDescription - Partner Employee extends Role - Salary Teacher extends Role - Classes Student extends Role - Grades I would like to avoid "hard coded" relationships in the partner class (meaning having properties pointing to every available role). In addition I need to be able to query the different roles, but also need to be able to show all "implemented" roles of a particular partner. What would be the best model to architect the mentioned scenario? Is there an option in extending Role and having a list of "implemented" roles in the Partner object? Does this all make sense or would you re-architect this whole problem differently? Would you denormalize and embed the Partner class in each of the role classes? Thanks, Mirko There are different options I see so far on how to and I would like to store the different facets -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
