Richard Nduka wrote:
I have the Users table which i have decided to use to stuff common fields and i have Teacher, Student and Parent which i have made to be subclasses of Users and which would store specific fields that are not common using the hibernate joined subclass per table strategy.
If you ever have any user with more than one role, this seems like it will lead to problems. Why not have the common stuff in user, and three separate 1-to-1 relationships (not-null=false) with the special purpose info?
Even if you don't do that, is there a difference between your "getUserType" and hibernate's "descriminator"?
-Dale --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
