Date: Fri, 13 Sep 2024 05:42:10 -0700 (PDT)
From: Rich Shepard <rshepard@appl-ecosys.com>
To: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: DDL issue
In-Reply-To: <CAG0dhZDFYNzCSvAgs3rTmnarXJrR38SLMRb96kq_0k+zam9ZjA@mail.gmail.com>
Message-ID: <be59e730-dc1f-2ecc-202d-ee837cc58f9f@appl-ecosys.com>
References: <91bda8-3bdb-d93-6c17-41a03a3de27a@appl-ecosys.com> <CAPnRvGt_=bWgTKaZSaK=K_TXJYHQ3oOJckvzUByfotCuGoMNzw@mail.gmail.com> <CAG0dhZDFYNzCSvAgs3rTmnarXJrR38SLMRb96kq_0k+zam9ZjA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://www.postgresql.org/message-id/be59e730-dc1f-2ecc-202d-ee837cc58f9f%40appl-ecosys.com>
Precedence: bulk

On Fri, 13 Sep 2024, Tony Shelver wrote:

> Or if you want to get even more flexible, where a dairy could have more
> than one owner as well as one owner having more than one dairy, you could
> create an intersection / relationship table.
>
> Something like
>
> -- Create people table (one entry per person)
> CREATE TABLE people_dairy_map ( pdm_id SERIAL PRIMARY KEY,
> first_name VARCHAR(100),
> last_name VARCHAR(100),
> email VARCHAR(100) UNIQUE );
> phone_number VARCHAR(15),
> person_id INT REFERENCES people(person_id)
> dairy_id INT REFERENCES dairies(dairy_id);

Thanks, Tony.

Regards,

Rich