5 ms·
Avoiding DB work strikes me as not the greatest reason to store JSON in your DB. But I find there are good reasons to do it. The main one for me is when the d
by jakejake 13y ago
Avoiding DB work strikes me as not the greatest reason to store JSON in your DB. But I find there are good reasons to do it. The main one for me is when the data fields are configurable by the user.
If I didn't want to be constrained by a schemas I'd just go with a NoSQL solution. Nothing wrong with that either.
- tensor 13y agoPostgres can make a pretty nice "nosql" solution too. Either via hstore, json, or bytea. That said, nothing frees you from a schema. Not having it explicit in the database just means you have it encoded into your application code.