Anonymous Coward writes:
"An article regarding adding support for a json variant to PostgreSQl appears interesting. From the article:
This work is a confluence of two projects - our hstore and json, which [have been] in PostgreSQL for years in somewhat incomplete forms - hstore (10 years old!) implements key-value storage with binary storage and indexing, while json - document storage implemented as a text. I and Teodor Sigaev have started working on nested hstore more than year ago with support of Engine Yard and got working prototype with everything document-oriented storage needed (see our presentations in Ottawa, 2013, Dublin, 2013, http://www.sai.msu.su/~megera/postgres/talks/), which eventually happens to be binary storage for jsonb - a new data type, introduced by Andrew Dunstan, which has everything from json, but performs better, thanks to binary representation and indexing ! jsonb doesn't preserve an order of keys and keys are unique ( the last win)."
Embedding the flexibility of document orientation into a column through the JSON datatype for me is the way to go. Pure document only style Use Cases are probably rare and I don't want to run a Mongo and a SQL if I can avoid that.
On a side note:- Anytime you get into an organisation their legacy is a nightmare. Having a schema is a bit of a relief. I don't wan to picture, 5 years from now, going into an organisation and trying to fix an agile developed Mongo Project.