> On 20 Oct 2025, at 14:55, Rich Shepard <rshepard@appl-ecosys.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
