Pretty neat. I think this is the important bit though:
"Basically, his patch just parses the text to make sure it was valid JSON, and stores it as text."
So, if you already have an environment where you are certain you are inserting valid JSON, it's not much different than just using the text type today.
> So, if you already have an environment where you are certain you are inserting valid JSON, it's not much different than just using the text type today.
Today, yes.
Tomorrow, when you launch an API and suddenly hundreds of different apps are talking to your systems, no.
Putting rich descriptions of data right next to the data is a good thing in the long run.
So, if you already have an environment where you are certain you are inserting valid JSON, it's not much different than just using the text type today.