Re: design problem computer-user-database
- From: John Vinson <jvinson@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Feb 2006 22:01:51 -0700
On 17 Feb 2006 16:18:47 -0800, "rpfd" <recipient@xxxxxxxxxxxxxxx>
wrote:
I guess the multiple computers add another dimension to the
whole thing...!
That's the clue that unravels the knot, actually!
You have a perfectly normal many (users) to many (computers)
relationship. The clue is that the password is an attribute, not of
the user, nor the computer, but of the *relationship* between the two
- and individual user on a particular computer.
You need three tables: * marks the Primary Key.
Users
*UserID
LastName
FirstName
<other info about the person>
Computers
*ComputerID
<information about the computer box>
Accounts
*UserID
*ComputerID
UserName <what is this user's account name on this box>
Password <for this account>
One user will have multiple records in the Accounts table; so will
each computer - but they'll each have a record for the username or
password (either of which could be duplicated with another record).
John W. Vinson[MVP]
.
- References:
- design problem computer-user-database
- From: rpfd
- design problem computer-user-database
- Prev by Date: Re: Is my design properly normalized?
- Next by Date: Queries, and how they multipy data
- Previous by thread: design problem computer-user-database
- Index(es):
Relevant Pages
|
