well. for now it can only be one contact and one address per
customer. the thing
is though, that also other people can have addresses and contacts. so
for example
there will be a user table or something like that. and a user will also have
address and contact information.
would you still recommend then to make a extra contact and adress table or
should the address and contact columns be just added in each of the tables
which needs them (like in that case cusstomers and users)
im especially interested in what performs better in mysql.. for
example is it an
performance advantage to have extra tables for addresses and contacts, since
not all of the queries will ask for the normal information, the
address information
and the contact information at the same time?
thanks alot in advance!
florian
>Well, you usualy split your data in tables for a reason, because some data in
>mulitple numbers are associated to one, or multiple data.
>
>In your case, if you have one address and contact per customers, then make it
>one table.
>If you have an unknown numer of contacts and numbers per customer, then make
>multiple tables.
>
>The joins will be on the primary keys (they should be at least). so it should
>be fast, even with 2 million records.
--
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
