Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Databases Microsoft

Unified NoSQL Query Language Launched 194

Posted by timothy
from the ontogeny-recapitulates-phylogeny dept.
splitenz writes "Hoping to unify the growing but disparate market of NoSQL databases, the creators behind CouchDB and SQLite have introduced a new query language for the format, called UnQL (Unstructured Data Query Language — .PS). It has Microsoft's backing."
This discussion has been archived. No new comments can be posted.

Unified NoSQL Query Language Launched

Comments Filter:
  • Re:Just in time! (Score:3, Interesting)

    by codepunk (167897) on Saturday July 30, 2011 @10:34AM (#36932612)

    "Fast-forward to the 2000s and 2010s."

    This is the issue, fast forwarding to 2010 we are dealing with scaling and environment issues that your precious relational database cannot solve.

    Tell me mr genius how you are going to handle 300k select queries on you mysql database holding 10 million rows, running on a virtual instance with shitty IO. Now add the fact that you have a very limited budget etc.

    NoSQL stores are designed to address this sort of scenario not your little app with a hundred concurrent users hanging off of it.

  • by AuMatar (183847) on Saturday July 30, 2011 @06:42PM (#36935696)

    And then you ha0ve a use case change. Or need to interface with an app written in another language. Or find that *shock* while a certain object is very effective for holding some information, it's a horrible way of storing for query. An object should be designed for the use case at hand, the database should be designed for efficient retrieval for that and future use cases. The two are damned near never the same. Persistence frameworks are a mistake.

Civilization, as we know it, will end sometime this evening. See SYSNOTE tomorrow for more information.