http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Daniel, Thanks, looks awesome. I wonder if there is a good way to get this without bringing the full parser in. http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment13http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment13Tue, 21 Aug 2012 17:07:25 GMTThanks for the clarification on the search index. I actually have several places in my app where this technique will be useful. Thanks.http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment12http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment12Tue, 21 Aug 2012 14:20:40 GMTI've extracted the query expression decompiler logic into a standalone program: https://gist.github.com/3414523 It might be a bit too aggressive though, sometimes it would be more readable to keep the lambdas around.http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment11http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment11Tue, 21 Aug 2012 11:03:31 GMTMatt, Thanks, typo fixed. Regarding the results, RavenDB has indexing model & query model, they don't have to quite match from types perspective, because we do a lot of funcy stuff. This index is explained here: http://ayende.com/blog/152833/orders-search-in-ravendbhttp://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment10http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment10Tue, 21 Aug 2012 10:28:32 GMTDaniel, We already have a dependency on NRefactory, although on the server, and not on the client, which is where this code is runnig. Any reference for how to use those two?http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment9http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment9Tue, 21 Aug 2012 10:26:25 GMTconfigurator, 1) Will be done. 2) Cannot really work. What happen if you already use x or y in your lambdas already? this0 it much less likely http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment8http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment8Tue, 21 Aug 2012 10:21:01 GMTRoy, Good idea, I'll see if that can be made to work.http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment7http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment7Tue, 21 Aug 2012 10:20:15 GMT@Matt That index is from this blog post http://ayende.com/blog/152833/orders-search-in-ravendb. And yes, the idea is that you can search across several fields at the same time. Also it's not a Map/Reduce query, it's just using ReduceResult as the type for the shape of the Map output.http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment6http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment6Fri, 17 Aug 2012 16:23:17 GMT"Then I had an affiany." I believe the word you wanted was "epiphany" One thing I don't quite get: In the reduce result, you specify Query as a string, but in the mapping it's clearly an array of objects. I thought that these had to match? Also (to repeat one of your favorite lines) - What are you actually trying to do here? If this is just an index of all of those properties, why do you need the array of objects at all? If I was to guess, it looks like the index is such that you can search across all of these fields at the same time? If so, is this the recommended approach, and is it written up somewhere that I can't seem to find?http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment5http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment5Fri, 17 Aug 2012 15:36:23 GMTHi, broken url... I can't see the url http://ayende.com/blog/157665/data-virtualization-lazy-loading-stealth-pagingndash-whatever-you-want-to-call-it-herersquo-s-how-to-do-it-in-silverlight?key=f69eddad-8e64-4363-94ac-2da433d52515&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+AyendeRahien+%28Ayende+%40+Rahien%29 http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment4http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment4Fri, 17 Aug 2012 14:44:01 GMTYou could also use the code from ILSpy that transforms C# LINQ calls back into query expressions. (IntroduceQueryExpressions and CombineQueryExpressions transforms) Those two are purely syntactic transformations, they don't consume any additional information from previous decompiler stages. Although pulling in a full-blown C# parser as a dependency might be overkill for this problem :)http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment3http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment3Fri, 17 Aug 2012 11:15:44 GMTThere are two changes I would make: 1. Substitute C# type aliases where appropriate. This isn't hard, and just needs a hard-coded list of the 15-or-so aliases that exist. (I wouldn't leave out the "System." or any other namespaci n other types, myself). 2. Use 'x', 'y' and 'z' instead of this0 (and presumably this1 and this2) - once you run out of those three - which I'm guessing you won't in 95% of cases - you can use an identifier with a number like this0 or x0. But using xyz first would make the entire thing a bit more readable. All in all, this is an awesome feature.http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment2http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment2Fri, 17 Aug 2012 09:58:54 GMTNice! Perhaps you could even leave out the "System." prefixes and "System.Object" altogether?http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment1http://ayende.com/157761/ravendb-awesome-feature-of-the-day-formatted-indexes#comment1Fri, 17 Aug 2012 09:25:28 GMT