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.
Recommended approach is to have separate tables.
Salahuddin (살라후딘) |
On Thu, 23 May 2024 at 08:39, Skorpeo Skorpeo <skorpeo11@xxxxxxxxx> 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.
