David, On Nov 15, 2013, at 10:34 AM, David Avendasora <[email protected]> wrote:
> Yeah, once you’ve abstracted the different properties and behaviors to > different Roles, those can all inherit from a common Role superclass, but > that is only really useful if there are attributes and relationships that you > need to save in the database that the different subclasses all have in > common, otherwise you are again forcing an architecture on something that > doesn’t really need it, and could become a limitation in the future. > I respectfully disagree. They at least share “Role Name” between them. AND, if you want to iterate over roles, and add new roles in the future, it’s much more convenient to have a to-many relationship for them. Ken
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
