| From: | Michał Kłeczek <michal(at)kleczek(dot)org> |
|---|---|
| To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Arrays vs separate tables |
| Date: | 2025-10-20 13:38:21 |
| Message-ID: | CC75487C-BBDF-474D-880A-87FB6CEED812@kleczek.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 20 Oct 2025, at 14:55, Rich Shepard <rshepard(at)appl-ecosys(dot)com> wrote:
>
> On Mon, 20 Oct 2025, Peter J. Holzer wrote:
>
>> * Simplicity: If a set of values is always fetched together and updated
>> together, you might as well treat it as a unit and not split it over
>> multiple tables
>
>> The second may be relevant for you. If you always display and edit the
>> phone numbers of a contact together and your frontend makes it easier to
>> edit an array than a subset of rows from a table, you might just stuff
>> them into a table and ignore "purity".
>
> Peter,
>
> Thank you. That's my use case.
There is also another concern - do you want to make sure phone numbers are not shared?
—
Michal
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2025-10-20 14:07:36 | Re: Arrays vs separate tables |
| Previous Message | Rob Sargent | 2025-10-20 13:26:32 | Re: Convert date and time colums to datetime |