On Thu, 2024-05-23 at 11:06 -0500, Skorpeo Skorpeo wrote:
> I see people are big fans of json here.
PostgreSQL's JSON support is great.
But way too often people use it in the wrong way.
Yours,
Laurenz Albe
On Thu, May 23, 2024, 10:07 Skorpeo Skorpeo wrote:
> Thank you for the valuable feedback. I see people are big fans of json
> here.
>
>>
It's better for data interchange than as a basis for long term model
storage.
David J.
On 5/23/24 09:06, Skorpeo Skorpeo wrote:
Thank you for the valuable feedback. I see people are big fans of json
here.
You can be a fan of JSON and still think it is not the correct way to
store data in a relational database. When you do that you often end up
with nested, possibly
Thank you for the valuable feedback. I see people are big fans of json
here.
On Thu, May 23, 2024 at 3:04 AM Laurenz Albe
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
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 json
> objects,
> for example "Users" and "Inventory", would it be ok to have one
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
On Wednesday, May 22, 2024, Skorpeo Skorpeo 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
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
