3 ms·
In my experience, you’re going to pay for that complexity at some point. You either pay it at the write end or the read/query end. I don’t see a way around tha
by mbreese 2y ago
In my experience, you’re going to pay for that complexity at some point. You either pay it at the write end or the read/query end.
I don’t see a way around that, so if PG explicitly makes it so that you pay it once on the write, I’m good with that.
The alternative is a more complicated data storage layout that makes queries more complicated. That’s okay too, but it just depends on your use case.
I prefer the stability and “correctness” of PG, but if more flexible queries are important to you, have at it. It’s nice to have more options for JSON storage.