Ayende @ Rahien

Afif commented on Rob’s Sprint: Result Transformers

Fri, 08 Mar 2013 01:57:27 GMT

and what if you wish to populate properties on a reduce result at query time? how can this be done with one round trip to the database

Barry Hagan commented on Rob’s Sprint: Result Transformers

Fri, 08 Mar 2013 00:32:18 GMT

This is really nice and clean. Especially on the Load calls to get a partial document directly from the database - I think a lot of people have been looking for that one.

Ayende Rahien commented on Rob’s Sprint: Result Transformers

Thu, 07 Mar 2013 14:37:21 GMT

Sean, This is a 2.5 feature.

Ayende Rahien commented on Rob’s Sprint: Result Transformers

Thu, 07 Mar 2013 14:37:00 GMT

Johanne, Yes, we are deprecating the TransformResults. And there is NO perf difference between the two. Both of those happened at _query time_, not at indexing time. And doing projections on the client side is only useful if you need the entire document. If you want to get just some of the data out, it is probably easier with result transformer.

Sean Feldman commented on Rob’s Sprint: Result Transformers

Thu, 07 Mar 2013 14:31:48 GMT

Is this in v2.0? http://ravendb.net/docs/2.0/ doesn't mention this...

Matt Warren commented on Rob’s Sprint: Result Transformers

Thu, 07 Mar 2013 12:19:06 GMT

@Johannes No the existing TR aren't materialised, they are only applied at query time. The new TR will work in the same way, but they difference is that they are de-coupled from an index, i.e they can be re-used by different indexes, you can use the same index with/without a TR etc. To materialise you need to use Store in the index. That puts the fields into the index where they can be fetched from, rather than having to go an get the entire doc from the doc store. See "Field Options" on http://ravendb.net/docs/client-api/querying/static-indexes/configuring-index-options With regards to TR v Loading and Include, it makes most sense to use a TR if you want to cut-down on network bandwidth. Loading via Include will pull back entire docs

Johannes Rudolph commented on Rob’s Sprint: Result Transformers

Thu, 07 Mar 2013 11:20:11 GMT

Does that mean TranformResults on idexes will be deprecated? Whats the cost of an index result transform vs these new standalone result tranforms? I thought (but may be wrong) that TransformResults as part of an index is materialized, so it's blazingly fast. Also, when in general would you advice using ResultTransformers vs. Loading a related document via .Include and the projecting viewmodels on the client?