Is there a reason you want to avoid hard coding roles? I can certainly
understand from an OO purists perspective why that can leave a nasty
aftertaste, but if you have a finite set of roles, it isn't the worst thing
in the world. In fact, it may simplify your overall design. To me, join
classes whe
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 abs
