JSON columns in Postgres can be flexible, but too much flexibility can be risky as you might accidentally end up with malformed data. You can prevent this using the pg_jsonschema extension to easily define a schema for your JSON and JSONB columns!

I'm all for using JSON schemas to enforce data consistency. In my experience, it's a great way to maintain data quality, especially when working with complex JSON data structures.

I’ve been curious about JSON columns. I have a couple use cases that would be solved with it. But is it seen as inefficient in cases of large datasets or large json sets? Cause I assume it’s like an index on an index when queried?

The performance of no schema with the rigidness of a schema

I came across this video at the perfect time, thanks!

Is not enough to store a string (json) in a text column?

Using a JSONB column allows you to filter the data using the properties of the column, and also allows you to index the column, so you can efficiently query the data. In addition to that, if you only want a certain property of the column and not the entire thing, you can do that too!