Ayende @ Rahien

Ofer commented on Searching ain’t simple: solution

Mon, 26 Mar 2012 07:00:00 GMT

Two typo corrections: 1. Change "descried" to "described" 2. Change "archiect" to "architect" (in the balsamiq GIF)

Vitaliy commented on Searching ain’t simple: solution

Sat, 24 Mar 2012 21:51:01 GMT

I may be missing the whole idea of the post, but what should be the solution if the label was "diagrams for architects"?

Martin Doms commented on Searching ain’t simple: solution

Sat, 24 Mar 2012 21:05:02 GMT

Is that q.Suggest() method provided by RavenDB, or is that an extension method that the application developer would implement? Is it the "string distance algorithm" you mentioned?

Paulo commented on Searching ain’t simple: solution

Sat, 24 Mar 2012 18:08:21 GMT

@Bill, thank you! I'll take a look at it!

Bill commented on Searching ain’t simple: solution

Sat, 24 Mar 2012 17:22:22 GMT

@Paulo, that looks like Sublime Text 2 - http://www.sublimetext.com/2

Paulo commented on Searching ain’t simple: solution

Sat, 24 Mar 2012 13:33:43 GMT

Sorry for the side question but... these screen caps aren't from Visual Studio IDE, are they?

Phillip commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 23:57:16 GMT

I don't like the name of the action when it can be searched by id as well as name... nit-picking tho. I've written something similar for my project, this stuff took way too long to do with a relational database, it really is frictionless.

Karep commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 19:44:06 GMT

I'd refactor that code. I don't like the return at the end of ArchitectsByName. If there are result return immedately. Guard condition.

Ayende Rahien commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 15:03:18 GMT

Peter, Yes, that is part of that.

peter commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 15:02:36 GMT

I see, you are using lucene SpellChecker. Can I assume it is using statistics from the indexed ravendb documents to determine order of suggested terms?

Ayende Rahien commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 14:58:29 GMT

Chris, Results = new NameAndId[0] -- Create a new empty array of NameAndId The reason that we have two generic params is that it is NOT possible for us to infer the first parameter from the second, and yes, there are reasons why you would have different values there.

Chris commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 14:44:34 GMT

I think there is a typo in the code second code sample. I'm not sure what "Results = new NameAndId[0]" is. Please forgive me if I am being dense, but why is it necessary to specify both the query type and the result type in Session.Query? It seems that Architects_Search.Result could be inferred since Architects_Search is declared to be AbstractIndexCreationTask. Is it possible for Session.Query to be called as Session.Query?

Jason Meckley commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 14:07:51 GMT

"And it turns out that when you think about it right, searching is simple." A large portion of this is because RavenDB does all the heavy lifting for us. All we need to do is map the results from RavenDB to our view model. Zero Friction FTW!

Ayende Rahien commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 14:00:53 GMT

Peter, That is done inside RavenDB, yes.

peter commented on Searching ain’t simple: solution

Fri, 23 Mar 2012 13:59:05 GMT

When you say "It does that by running a string distance algorithm" do you mean you already have this capability implemented in RavenDB? Is it something like this one (what we ended up using inhouse): https://github.com/lorenzo-stoakes/spell-correct His implementation discussed here: http://www.codegrunt.co.uk/2010/11/02/C-Sharp-Norvig-Spelling-Corrector.html