Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,128 | Comments: 45,551

filter by tags archive

Implementing a document database: simple queries

time to read 3 min | 457 words

And now this passes:

public class PerformingQueries
    const string query = @"
var pagesByTitle = 
from doc in docs
where doc.type == ""page""
select new { Key = doc.title, Value = doc.content, Size = (int)doc.size };

    public void Can_query_json()
        var serializer = new JsonSerializer();
        var docs = (JArray)serializer.Deserialize(
                new JsonTextReader(
                    new StringReader(
{'type':'page', title: 'hello', content: 'foobar', size: 2},
{'type':'page', title: 'there', content: 'foobar 2', size: 3},
{'type':'revision', size: 4}
        var compiled = new LinqTransformer(query, "docs", typeof(JsonDynamicObject)).Compile();
        var compiledQuery = (AbstractViewGenerator<JsonDynamicObject>)Activator.CreateInstance(compiled);
        var actual = compiledQuery.Execute(docs.Select(x => new JsonDynamicObject(x)))
        var expected = new[]
            "{ Key = hello, Value = foobar, Size = 2 }",
            "{ Key = there, Value = foobar 2, Size = 3 }"

        Assert.Equal(expected.Length, actual.Length);
        for (var i = 0; i < expected.Length; i++)
            Assert.Equal(expected[i], actual[i].ToString());

You wouldn’t believe how much effort it took, and all in all, implementing this is about 500 lines of code or so.



So do we take it this is a sponsored effort or could you not help yourself ;-)

I take it the comment on effort was sarcasm? Regardless you are a legend.

James Newton-King

I'm hoping the effort was parsing and creating the query and not working with Json.NET :)

Ayende Rahien


I have exactly 2 problems with Json.NET

1) I don't like the way I need JsonTextReader -> StringReader just to deserialize a string

2) R# has a bug that made me thing that I cannot access the Value property of JProperty.

2) is not your fault.

Other than that, it is lovely.


Ayende, was the effor related to supporting Linq? Would it be the same if you implemented the same functionality with Boo / rhino dsl?

Ayende Rahien


Boo would give me different syntax, not as set based as this.

The effort was mainly in how to take the query and make it executable

James Newton-King

Ayende you could use JsonConvert.DeserializeObject without any type parameter to deserialize the string to a JArray. That would let you do it in one line and save having to create a JsonSerializer, JsonTextReader and StringReader.


What are you using to parse / compile the LINQ? Are you doing it by hand, using a grammar, or just using CodeDom?

Ayende Rahien


A lot of magic and the C# compiler

Nathan OSullivan

One thing I'm not getting in this series is what is the persistence strategy for your views?

Chris Martin

...and it looks like ass.

Sorry but, you're fired! ;)

Comment preview

Comments have been closed on this topic.


  1. The worker pattern - 8 hours from now

There are posts all the way to May 30, 2016


  1. The design of RavenDB 4.0 (14):
    26 May 2016 - The client side
  2. RavenDB 3.5 whirl wind tour (14):
    25 May 2016 - Got anything to declare, ya smuggler?
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats