Discussion about this post

User's avatar
robert schaefer's avatar

Hi,

I tried coding the example starting at CREATE TABLE customers, then INSERT, then SELECT.

At the 3 different SELECTS, I could not get a data match return value for the third example

without changes. For the 3rd SELECT I changed "promotion code" to "purchases".

I'd like to know what to change in the first two SELECTs to get a match, and possibly

an explanation of the operator "@>", what goes where into the fields, and why.

Thank you,

Expand full comment
Tushar Kardile's avatar

Thank you for the insightful article and detailed explanation. JSONB's schema-less design initially makes it seem like a desirable choice. But as data volume increases, significant performance issues may arise, especially with regards to read delay brought on by the overhead of serialization and deserialization. Furthermore, keeping big payloads in JSONB columns could make backup and restoration more difficult, which could affect system recovery times and dependability.

Consequently, using JSONB should be a conscious design decision based on a thorough comprehension of the long-term effects on performance, maintainability, and scalability. Carefully weighing the trade-offs and coordinating them with the larger system design and operational objectives is essential.

Expand full comment
3 more comments...

No posts