I don't agree :). SQL nicely abstracts what would have been more difficult or technical to do otherwise. Yep, it was create in order to enable non strictly technical people to query their data, but does it make it bad? I don't think so. Also authors of great many NoSql databases (and other technologies, ever heard about the widely loved LINQ technology in C#?) think, giving their users the possibility to query data using what they already know. Also: can you honestly, from the bottom of your heart, say that you'd rather filter json documents using some form of XPath? Besides: I'm not trying to criticize relational model, as well as I'm not saying that JSON is the way to go when storing data :D I just wanted to create a tool for people that are trying to implement a very specific business case I described and, due to lack of tools, are having some issues with it.

> Also: can you honestly, from the bottom of your heart, say that you'd rather filter json documents using some form of XPath?

Come one read the second line of my reply before strawmanning.

Ok, maybe I got too defensive and assigned to much weight to the first part of your first sentence. No strawmanning intended :)

Also: please look at my first comment, from 13 hours ago - it should shed some light on the "why" part.