| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: DDL issue |
| Date: | 2024-09-13 16:27:33 |
| Message-ID: | c8a264d-51c-5ccf-2d1-d93e2686c97d@appl-ecosys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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,
This comes close; I need to think about this.
Thanks,
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Mullineux | 2024-09-13 16:58:43 | Re: Will hundred of thousands of this type of query cause Parsing issue |
| Previous Message | Willow Chargin | 2024-09-13 16:12:12 | Re: Functionally dependent columns in SELECT DISTINCT |