public inbox for [email protected]
help / color / mirror / Atom feedFrom: Muhammad Salahuddin Manzoor <[email protected]>
To: Skorpeo Skorpeo <[email protected]>
Cc: [email protected]
Subject: Re: Json table/column design question
Date: Thu, 23 May 2024 09:01:16 +0500
Message-ID: <CAKD7CD=aoXdRMLjOWR-S+TPgMqWGiY9Wn7RgTG4nkVgwgBR99w@mail.gmail.com> (raw)
In-Reply-To: <CAMXrOMOav1m8Ep01o7_GDLWxLSpgMp+o4d3FNdmOY7RoWe5B7Q@mail.gmail.com>
References: <CAMXrOMOav1m8Ep01o7_GDLWxLSpgMp+o4d3FNdmOY7RoWe5B7Q@mail.gmail.com>
Greetings,
Storing unrelated JSON objects in the same table with distinct columns for
each type (e.g., "Users" and "Inventory") is generally not a sound good
approach may affect Query Performance and Optimization, Storage Efficiency,
scalability and Maintenance, Data Integrity.
Recommended approach is to have separate tables.
*Salahuddin (μ΄λΌνλ*
*)*
On Thu, 23 May 2024 at 08:39, Skorpeo Skorpeo <[email protected]> wrote:
> 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.
>
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: Json table/column design question
In-Reply-To: <CAKD7CD=aoXdRMLjOWR-S+TPgMqWGiY9Wn7RgTG4nkVgwgBR99w@mail.gmail.com>
* 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