public inbox for [email protected]  

help / color / mirror / Atom feed

From: Michał Kłeczek <[email protected]>
To: Rich Shepard <[email protected]>
Cc: [email protected]
Subject: Re: Arrays vs separate tables
Date: Mon, 20 Oct 2025 15:38:21 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<pyh2kcisxwrhzz255gaiaawo5yubirdifzsfvz3okqcjeaaqqr@6lq5n6idswg7>
	<[email protected]>


> On 20 Oct 2025, at 14:55, Rich Shepard <[email protected]> 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

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Arrays vs separate tables
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox