people and another one for the n addresses of your
>>>>people.
>>>>
>>>>If you keep your current schema, you will have as many rows for one
>>>>person
>>>>as many addresses for that person you have, and you will be
>>>>duplica
ople and
another for
your people's addresses.
-----Original Message-----
From: tony yau [mailto:[EMAIL PROTECTED]
Sent: Viernes, 13 de Mayo de 2005 09:27 a.m.
To: php-db@lists.php.net
Subject: [PHP-DB] novice on table design
Hi all,
I have the following tables
EmployeeCustomer
>> people.
> >>
> >> If you keep your current schema, you will have as many rows for one
> >> person
> >> as many addresses for that person you have, and you will be
> >> duplicating
> > many
> >> fields. So you must split you
hat person you have, and you will be
duplicating
many
fields. So you must split your tables, one for your people and
another for
your people's addresses.
-Original Message-
From: tony yau [mailto:[EMAIL PROTECTED]
Sent: Viernes, 13 de Mayo de 2005 09:27 a.m.
To: php-db@lists.php.net
Sub
;s addresses.
>
> -Original Message-
> From: tony yau [mailto:[EMAIL PROTECTED]
> Sent: Viernes, 13 de Mayo de 2005 09:27 a.m.
> To: php-db@lists.php.net
> Subject: [PHP-DB] novice on table design
>
>
>
> Hi all,
>
>
p.net
Subject: [PHP-DB] novice on table design
Hi all,
I have the following tables
EmployeeCustomernon-CustomerAddress
=======
pkey pkeypkey
pkey
n
Hi all,
I have the following tables
EmployeeCustomernon-CustomerAddress
=======
pkey pkeypkey
pkey
number type type
...