So I'm using both types in a current personal project and I have to agree with the comment on the blog post
"[...] I use JSON for external application data that doesn’t need to be interpreted by say, an SQL function or a trigger. Basically storage-only data..."
Basically I use hstore's as meta columns, for say a one off attribute of a model that I dont want to have as another column and have to do a migration. It is leaps and bounds better than using a text column because you can query.
JSON I use for basically caching api calls. For instance I save off the json from the itunes api for all of the albums of an artist or all of their songs.
It will be awesome when 9.3 comes out and you can query that though. That will be something.
"[...] I use JSON for external application data that doesn’t need to be interpreted by say, an SQL function or a trigger. Basically storage-only data..."
Basically I use hstore's as meta columns, for say a one off attribute of a model that I dont want to have as another column and have to do a migration. It is leaps and bounds better than using a text column because you can query.
JSON I use for basically caching api calls. For instance I save off the json from the itunes api for all of the albums of an artist or all of their songs.
It will be awesome when 9.3 comes out and you can query that though. That will be something.