MIME-Version: 1.0
From: Skorpeo Skorpeo <skorpeo11@gmail.com>
Date: Wed, 22 May 2024 22:38:23 -0500
Message-ID: <CAMXrOMOav1m8Ep01o7_GDLWxLSpgMp+o4d3FNdmOY7RoWe5B7Q@mail.gmail.com>
Subject: Json table/column design question
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000008dc025061916ca49"
Archived-At: <https://www.postgresql.org/message-id/CAMXrOMOav1m8Ep01o7_GDLWxLSpgMp%2Bo4d3FNdmOY7RoWe5B7Q%40mail.gmail.com>
Precedence: bulk

--0000000000008dc025061916ca49
Content-Type: text/plain; charset="UTF-8"

Hi,

I was wondering if having unrelated columns in a table is a sound approach
when using json.  In other words, if I have two collections of unrelated
json objects, for example "Users" and "Inventory", would it be ok to have
one table with a "Users" column and a "Inventory" column?  My concern is
that from a row perspective the columns could be different lengths, such as
more inventory items as users.  And for any given row the data in one
column would have no relation to another column. I would only query a
single column at a time.

Would this approach be ok or are there pitfalls such that it would be
advantageous/recommended to have a separate table for each column?

Any thoughts/inputs are greatly appreciated.

Many thanks.

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

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>I was wondering if havin=
g unrelated columns in a table is a sound approach when using json.=C2=A0 I=
n other words, if I have two collections of unrelated json objects, for exa=
mple &quot;Users&quot; and &quot;Inventory&quot;, would it be ok to have on=
e table with a &quot;Users&quot; column and a &quot;Inventory&quot; column?=
=C2=A0 My concern is that from a row perspective the columns could be diffe=
rent lengths, such as more inventory items as users.=C2=A0 And for any give=
n row the data in one column would have no relation to another column. I wo=
uld only query a single column at a time.</div><div><br></div><div>Would th=
is approach be ok or are there pitfalls such that it would be advantageous/=
recommended to have a separate table for each column?</div><div><br></div><=
div>Any thoughts/inputs are greatly appreciated.</div><div><br></div><div>M=
any thanks.<br></div></div>

--0000000000008dc025061916ca49--