News for hackers. Stuff that matters.
Re:JSON Support in SQL Server 2016 by baq on Tuesday May 19, 2015 @03:44AM (#9568579)
turns out relational databases make for quite good nosql datastores, it just takes a little bit of thought instead of jumping onto a bandwagon of the month.
Re:JSON Support in SQL Server 2016 by ahachete on Tuesday May 19, 2015 @06:50AM (#9569082)
Or not ^_^ Have a look at ToroDB (https://github.com/torodb/torodb). It is a mongo-compatible database sitting on top of PostgreSQL. You don't need thought, just use it :)

Disclaimer: I'm a ToroDB developer

Re:JSON Support in SQL Server 2016 by ahachete on Tuesday May 19, 2015 @07:22AM (#9569205)
Surprised by the downvote. It is an open source solution that does exactly what the parent comment was asking (not having to think about how to map json to a relational database). I don't see a problem mentioning some software (again: open source) as a viable solution to that problem.
Re:JSON Support in SQL Server 2016 by threeseed on Tuesday May 19, 2015 @08:12AM (#9569433)
It's trendy on HN to like SQL databases and bash MongoDB.
Re:JSON Support in SQL Server 2016 by moron4hire on Tuesday May 19, 2015 @09:58AM (#9570048)
Really? I thought it was the other way around.

Try not to make generalizations of a rather diverse crowd.

Re:JSON Support in SQL Server 2016 by ahachete on Tuesday May 19, 2015 @08:43AM (#9569597)
I know. But there was no MongoDB bashing -- at least in the comment ;)
Re:JSON Support in SQL Server 2016 by M8 on Tuesday May 19, 2015 @04:23AM (#9568685)
SQL =>

Step 1: remove data integrity.

Step 2: remove powerful query language.

Step 3: only store strings.

=> No-SQL

It's interesting that the technology is named after a missing feature.

Re:JSON Support in SQL Server 2016 by dorfsmay on Tuesday May 19, 2015 @09:57AM (#9570030)
As someone who had to do aggregation on hstore... Gosh! Why? It's not that difficult to add a column!
Re:JSON Support in SQL Server 2016 by threeseed on Tuesday May 19, 2015 @04:47AM (#9568747)
So I take it you have zero experience with NoSQL databases then.

HiveQL is far more powerful than SQL and MongoDB QL is pretty powerful for querying document data structures. The others do 95% of what most people are doing in SQL. And the overwhelming majority of NoSQL databases support data types.

And there is no issue with the data integrity of NoSQL databases. Do you really think the hundreds of top companies would use them if there was e.g. Apple, Google, Twitter, Netflix etc.

Re:JSON Support in SQL Server 2016 by pjmlp on Tuesday May 19, 2015 @04:17AM (#9568672)
With the added value of constraints and data integrity.

I am yet to do any project where a NoSQL database makes sense.