Feedback-ID: i76984098:Fastmail
Message-ID: <a15a61f9-eb6d-47b0-ad15-ab6ff39a0dd7@aklaver.com>
Date: Thu, 12 Sep 2024 16:46:51 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: DDL issue
To: Rich Shepard <rshepard@appl-ecosys.com>, pgsql-general@postgresql.org
References: <91bda8-3bdb-d93-6c17-41a03a3de27a@appl-ecosys.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <91bda8-3bdb-d93-6c17-41a03a3de27a@appl-ecosys.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/a15a61f9-eb6d-47b0-ad15-ab6ff39a0dd7%40aklaver.com>
Precedence: bulk

On 9/12/24 16:01, Rich Shepard wrote:
> I have one name in the people table who owns 5 different dairies with three
> different phone numbers, but all 5 have the the same email address.
> 
> The five dairies each has its own name and location while the people table
> has five rows with the same last and first names and email address.
> 
> Is there a way to have only one entry for the owner in the people table
> while related to five different company names? In some industries, such as
> dairy farms, this is not an unusual situation.

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.

> 
> TIA,
> 
> Rich
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com