Re: Portal Database design help

[Shine Jones]

well thanks,
I understand yes..
but why no..?
i mean what else you think needs modifications.

yeah, i understand what you mean, by changing phone numbers from columns to rows.ok..

and other than that..do you think i need some modifications.

i have one more confusion. as i am going to fetch all the fields from different tables in a one go.
either i need to choose joins or multiple queries. which is a compromise with speed when it comes out to be a huge database.i am not sure i am right but according to the research i have concluded that joins eat up the speed. as you know it is going to be a portal so i expect good traffic. what do you think.
and what is the extend to which i can split up my tables to reach better normalization..?

can you help out me with a proper example that how can i use phones as rows rather than columns..?

and what do you mean by this
<<<----
Another approach (assuming you never need to search on numbers):
contact_numbers table
company_id | numbers
where 'number' is a string looking like (say):
"phones: 321-432-2300, 321-432-2301; fax: [phone]"
In other words, human readable, but otherwise an arbitrarily formatted string.

Any of the above will "work". You will find out later which works best in your situation.
--->>>>