| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Arrays vs separate tables |
| Date: | 2025-10-20 14:32:22 |
| Message-ID: | 4b52b41-49ce-9be5-d9d8-104a3f43dfc1@appl-ecosys.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 20 Oct 2025, Ron Johnson wrote:
> Multiple contacts at the same client company. If, for whatever reason, the
> phone number changes you've got to update X rows in your contacts table,
> whereas only one row needs to be updated when the schema meets 1NF. This
> eliminates update anomalies.
Ron,
Not an issue: the companies table has a 'phone' column while the people
table has both 'direct_phone' and 'cellphone' columns. And, the locations
table has a 'loc_phone' column because many industrial companies have
multiple facilities.
Regards,
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-10-20 14:42:01 | Re: Arrays vs separate tables |
| Previous Message | Rich Shepard | 2025-10-20 14:25:56 | Re: Arrays vs separate tables |