Database Normalization Help!!!

[kenle]

I am developing a web application for a model agency.

I just have a question that for the model table, should I store all the info of the model users include username, passwd, address, models info (height, weight, hair color ...) and credit card info into one table. Is it ok or i have to somehow separate it?

If separate into many tables, can you explain the reason? I am new at this and would like to learn about this.

Thanks

[AshtrayWaterloo]

I think the only reason that you would want to add more tables is to be able to re-use common types. For example, in the credit card information you might want to have a small table containing a list of types of credit cards, i.e. Visa, Mastercard, American Express, etc. Use a two column table to do that: cc_type_id, and cc_type_narrative or whatever.

To normalize the database do this with all of the reusable types such as hair-colour and whatever else you have. Other than that, you're database would be OK.

Ash

[drawmack]

according to the rules of normalization the logic chain goes something like this

is it an autonomous object?
yes = one table
no ->

how many autonomous objects is it?

So what you have is this

a modle object -> name, b-day, ss, height, weight, hair-color, etc.

a credit card object -> owner (foreign key to modle), type, number, exp-date

etc.

my rule of thumb is if I have more then 10 fields in a table it probably isn't normalized very well.