hi.

Rick Schumeyer wrote:
[...]
 From a business rules perspective:
  Some users are not employees (like an admin user)
  Some employees are not users
[...]
from my view users and employees have something in common: they are persons.

why don't create a person-table with the attributes the groups share, like a login-name, etc.

then your users-table will have a primary-key that is also a foreign-key, referencing the id in the person-table and the employees-table does the same.

when you want to get all user- and employee-accounts for one person you have to build up a join on the tables. that's a simple view, don't know what your favourite or-mapper thinks about it.

i think the above table-design can be considered 'clean' from some academic point of view ;)

mfg

alexander

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

              http://archives.postgresql.org/

Reply via email to