Slash Boxes

SoylentNews is people

posted by janrinok on Monday March 24 2014, @08:28PM   Printer-friendly
from the jason-who? dept.

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,, 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)."

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Insightful) by fishybell on Monday March 24 2014, @09:25PM

    by fishybell (3156) on Monday March 24 2014, @09:25PM (#20570)

    For many applications, ACID compliance is truly key, but the ability to scale horizontally and store application data seamlessly have been, AFAIK, the major reasons to drop ACID in favor MongoDB and its ilk. Now that there is better support for replication -- with multi-master replication on the horizon -- and this new update, Postgres once again proves that while it doesn't cover 100% of use cases you can think of today, it will eventually. (side note, — doesn't seem to work)

  • (Score: 2, Interesting) by Zwerg_Sense on Monday March 24 2014, @09:46PM

    by Zwerg_Sense (927) on Monday March 24 2014, @09:46PM (#20584)

    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.