Normalization

Hello guys!
Can u please help me out?
Which way should i make my tables?
Customer
--
ID (Pk)
Name
Address
Login
Password
or
Customer
--
ID (Pk)
Name
Address
Permission
--
CustomerID (Fk Pk)
Login
Password
Thanks for your help,
Bruno NIn news:uWay4VVKFHA.732@.TK2MSFTNGP12.phx.gbl,
Bruno N <nylren@.hotmail.com> said:
> Hello guys!
> Can u please help me out?
> Customer
> --
> ID (Pk)
> Name
> Address
>
> Permission
> --
> CustomerID (Fk Pk)
> Login
> Password
This way, and in doing so you can give each customer more than one
permission should the need arise.
Steve|||Bruno
First of all I would not store passwords in the database as logins as well.
There are some discussions for the subject in this NG.
Actully every attribute should be depened on PK.
In that case I'd go with first one ,because Permission table actually does
not store any permisions for the customer.
"Bruno N" <nylren@.hotmail.com> wrote in message
news:uWay4VVKFHA.732@.TK2MSFTNGP12.phx.gbl...
> Hello guys!
> Can u please help me out?
> Which way should i make my tables?
> Customer
> --
> ID (Pk)
> Name
> Address
> Login
> Password
>
> or
>
> Customer
> --
> ID (Pk)
> Name
> Address
>
> Permission
> --
> CustomerID (Fk Pk)
> Login
> Password
>
> Thanks for your help,
> Bruno N
>|||>> Which way should i make my tables?
Only you would know, since you are the one who is familiar with your
business model.
A specific logical design and higher levels of normalization are done based
on the rules derived from a specific business model. Others here -- who are
unfamiliar with your business model -- can only make wild guesses, which in
many cases could be misguidance.
Anith