MIME-Version: 1.0
References: <CAMXrOMOav1m8Ep01o7_GDLWxLSpgMp+o4d3FNdmOY7RoWe5B7Q@mail.gmail.com>
 <f053e31c3c2e40541406ce4c266818dbbcfca7b2.camel@cybertec.at>
In-Reply-To: <f053e31c3c2e40541406ce4c266818dbbcfca7b2.camel@cybertec.at>
From: Skorpeo Skorpeo <skorpeo11@gmail.com>
Date: Thu, 23 May 2024 11:06:54 -0500
Message-ID: <CAMXrOMOY_ky6z8W4Fh=FoWdPB5xd12ZBeCj4JMqiu4eU7s97hQ@mail.gmail.com>
Subject: Re: Json table/column design question
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000079524c0619213f73"
Archived-At: <https://www.postgresql.org/message-id/CAMXrOMOY_ky6z8W4Fh%3DFoWdPB5xd12ZBeCj4JMqiu4eU7s97hQ%40mail.gmail.com>
Precedence: bulk

--00000000000079524c0619213f73
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you for the valuable feedback.  I see people are big fans of json
here.

On Thu, May 23, 2024 at 3:04=E2=80=AFAM Laurenz Albe <laurenz.albe@cybertec=
.at>
wrote:

> On Wed, 2024-05-22 at 22:38 -0500, Skorpeo Skorpeo wrote:
> > 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 jso=
n
> 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 hav=
e
> no
> > relation to another column. I would only query a single column at a tim=
e.
> >
> > Would this approach be ok or are there pitfalls such that it would be
> > advantageous/recommended to have a separate table for each column?
>
> It doesn't matter much if you use one or two columns.
> But the word "collection" makes me worry.  Perhaps this article can give
> you some ideas:
>
> https://www.cybertec-postgresql.com/en/json-postgresql-how-to-use-it-righ=
t/
>
> Yours,
> Laurenz Albe
>

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

<div dir=3D"ltr">Thank you for the valuable feedback.=C2=A0 I see people ar=
e big fans of json here.<br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, May 23, 2024 at 3:04=E2=80=AFAM Laure=
nz Albe &lt;<a href=3D"mailto:laurenz.albe@cybertec.at">laurenz.albe@cybert=
ec.at</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">On Wed, 2024-05-22 at 22:38 -0500, Skorpeo Skorpeo wrote:<br>
&gt; I was wondering if having unrelated columns in a table is a sound appr=
oach when<br>
&gt; using json.=C2=A0 In other words, if I have two collections of unrelat=
ed json objects,<br>
&gt; for example &quot;Users&quot; and &quot;Inventory&quot;, would it be o=
k to have one table with a<br>
&gt; &quot;Users&quot; column and a &quot;Inventory&quot; column?=C2=A0 My =
concern is that from a row<br>
&gt; perspective the columns could be different lengths, such as more inven=
tory<br>
&gt; items as users.=C2=A0 And for any given row the data in one column wou=
ld have no<br>
&gt; relation to another column. I would only query a single column at a ti=
me.<br>
&gt; <br>
&gt; Would this approach be ok or are there pitfalls such that it would be<=
br>
&gt; advantageous/recommended to have a separate table for each column?<br>
<br>
It doesn&#39;t matter much if you use one or two columns.<br>
But the word &quot;collection&quot; makes me worry.=C2=A0 Perhaps this arti=
cle can give<br>
you some ideas:<br>
<br>
<a href=3D"https://www.cybertec-postgresql.com/en/json-postgresql-how-to-us=
e-it-right/" rel=3D"noreferrer" target=3D"_blank">https://www.cybertec-post=
gresql.com/en/json-postgresql-how-to-use-it-right/</a><br>
<br>
Yours,<br>
Laurenz Albe<br>
</blockquote></div>

--00000000000079524c0619213f73--