Ayende @ Rahien

Hi!
My name is Ayende Rahien
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

@

Posts: 5,947 | Comments: 44,544

filter by tags archive

Querying relative information with RavenDB


Originally posted at 12/3/2010

Let us say that we have the following document:

{
  "Name": "Ayende",
  "LastScore": 239.2,
  "MaxScore": 392.6
}

And we want to find all documents whose last score is within a certain range from their max score. Note that for different queries, the range that I can use may be different.

RavenDB doesn’t offer the option of doing computation in the where clause. Mostly, that is because such computations are going to perform badly unless special care is taken to avoid that. Instead, we are going to create a computed field in the index.

First, we define:

from u in docs.Users
where u.MaxScore
select new { Score = u.LastScore / u.MaxScore } 

This computed field now allows us to query on it very easily. Moreover, when we query, we are still querying over pre-computed data, which is going to blindingly fast.


Comments

Patrick Huizinga

I don't get it.

How can you do a 'where' on a float? Or is this some RavenDB specific interpretation of Where?

note: my knowledge of RavenDB goes no further than what I picked up from this blog.

Ori
Ori

its a typeo no?

GStearns

It looks like he's making sure MaxScore is not 0 or null, which would cause the division to blow up

Bryan

He's also selecting the score, not the document. I don't know how you're supposed to get the document from the score.

I think he rushed the post a bit. :)

Rafal

Nitpick: this is not querying relative information like the title says. This is transforming relative to non-relative and querying only absolute values.

Sekhat

@Rafal yes, but if the document changes, the index gets updated so the value gets recomputed, so it works the result is the same as if you queried relative information.

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

No future posts left, oh my!

RECENT SERIES

  1. RavenDB Sharding (3):
    22 May 2015 - Adding a new shard to an existing cluster, splitting the shard
  2. The RavenDB Comic Strip (2):
    20 May 2015 - Part II – a team in trouble!
  3. Challenge (45):
    28 Apr 2015 - What is the meaning of this change?
  4. Interview question (2):
    30 Mar 2015 - fix the index
  5. Excerpts from the RavenDB Performance team report (20):
    20 Feb 2015 - Optimizing Compare – The circle of life (a post-mortem)
View all series

RECENT COMMENTS

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats