by sanityinc on 2/18/14, 11:32 AM with 8 comments
by sanityinc on 2/18/14, 11:35 AM
Priceless.
by raphinou on 2/18/14, 1:04 PM
by chris_wot on 2/18/14, 12:35 PM
However, unlike a relational engine which uses a query plan, you need to actually tell the aggregation engine in which order to process the data.
Doesn't this seem a little... backward? If the dataset is complex enough, the two things that come to mind are:
1. There would be a lot of redundancy in the hierarchical dataset.
and
2. That seems like a lot of futzing around to get the most optimal aggregation path!
What am I missing here?
p.s. I do tend to agree that the SQL syntax is rather more readable, but then again I've been looking at SQL for a lot longer than I have JSON style queries. The first query is not that unreadable!
1. http://thecodebarbarian.wordpress.com/2014/02/14/crunching-3...
by taylonr on 2/18/14, 2:32 PM