| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Arrays vs separate tables |
| Date: | 2025-10-20 14:25:43 |
| Message-ID: | CANzqJaC8JrirUM7Duu9Pp4vdLU85GdqSv6BcduamquFYz13kMg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Oct 20, 2025 at 10:07 AM Rich Shepard <rshepard(at)appl-ecosys(dot)com>
wrote:
> On Mon, 20 Oct 2025, Michał Kłeczek wrote:
>
> > There is also another concern - do you want to make sure phone numbers
> are
> > not shared?
>
> Michal,
>
> Shared with whom? I run a solo professional services consultancy so there's
> only me here the database.
>
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.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2025-10-20 14:25:56 | Re: Arrays vs separate tables |
| Previous Message | Michał Kłeczek | 2025-10-20 14:21:09 | Re: Arrays vs separate tables |