Date: Fri, 13 Sep 2024 05:38:30 -0700 (PDT)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general@postgresql.org
Subject: Re: DDL issue
In-Reply-To: <a15a61f9-eb6d-47b0-ad15-ab6ff39a0dd7@aklaver.com>
Message-ID: <4fb4a8d4-5f3a-b4aa-6b10-8b95d349941@appl-ecosys.com>
References: <91bda8-3bdb-d93-6c17-41a03a3de27a@appl-ecosys.com> <a15a61f9-eb6d-47b0-ad15-ab6ff39a0dd7@aklaver.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://www.postgresql.org/message-id/4fb4a8d4-5f3a-b4aa-6b10-8b95d349941%40appl-ecosys.com>
Precedence: bulk

On Thu, 12 Sep 2024, Adrian Klaver wrote:

> Quick and dirty:
>
> people_table
>   person_id  PK
>   name_last
>   name_first
>   email_address
>   ph_number
>   ...
>
> location_table
>   loc_id   PK
>   person_id_fk FK <--> people_table(person_id)
>   loc_name
>   loc_st_addr
>   loc_st_city
>   loc_st_st_prov
>   ...
>
> contact_table
>   contact_id  PK
>   loc_id_fk   FK <--> location_table(loc_id)
>   contact_ph_number
>   contact_email  --Can be null
>
> It can get more involved then this, depends on how flexible you want to get.

Adrian,

There are many companies with multiple locations, but few owners with
multiple companies, each with a different location. David's reminder about
many-to-many tables will do the job.

Thanks,

Rich