>> I need to have an EMPLOYEE_PROFILE table and GUEST_PROFILE table
that both have a PK of USER_ID. USER_ID must be unique for both
tables <<
Why not one table with a flag that tells you if this is a guest or an
employee? leanb out the guests when you are finished with them --
say, by looking at a time stamp ("Guests and fish smell bad after
three days" - Chinese Proverb). I am assuming that guests look like a
special case of employees, but with limits on their access rights.
These limitations could be put into DEFAULT clauses, so that just
getting the guest would automatically create the right profile.
Received on Fri Oct 26 2001 - 19:05:52 CDT
