MIME-Version: 1.0
References: <A5EB2191-62F9-44D3-8488-9C67DC033453@leisi.net>
In-Reply-To: <A5EB2191-62F9-44D3-8488-9C67DC033453@leisi.net>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 11 Sep 2024 09:24:16 -0400
Message-ID: <CAKAnmmKsOc=qoPo8XeR2ayTgRHwn8O747mxtohDc59Bbq4_e8w@mail.gmail.com>
Subject: Re: Database schema for "custom fields"
To: Matthias Leisi <matthias@leisi.net>
Cc: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000005d94550621d7ead9"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmKsOc%3DqoPo8XeR2ayTgRHwn8O747mxtohDc59Bbq4_e8w%40mail.gmail.com>
Precedence: bulk

--0000000000005d94550621d7ead9
Content-Type: text/plain; charset="UTF-8"

I'd go with option 2 (jsonb), as it's likely already well supported by your
applications, while the other approaches will require a good bit of
customization. JSONB can be indexed, so performance should be on par with
"traditional" tables.

Cheers,
Greg

--0000000000005d94550621d7ead9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;d go with option 2 (jsonb), as it&#39;s likely alrea=
dy well supported by your applications, while the other approaches will req=
uire a good bit of customization. JSONB can be indexed, so performance shou=
ld be on par with &quot;traditional&quot; tables.<div><br></div><div>Cheers=
,</div><div>Greg</div><div><br></div></div>

--0000000000005d94550621d7ead9--