No I don't want to do a multiple level include, I'm exploring allowing 1 type of document (Thing) to have multiple types of owners and from what Itamar said it should. Actually typing out code this should be the real usage correct?
This almost seems wrong as I really want to get back a company or a person depending on Owner, but I see it's setup like this so i can properly use strongly typed access to reach x=>x.Owner of Thing, correct? That using less strong typing that it would be the same as: Session.Include("Owner").Load<Thing>("things/1"); correct?
And what it does is pull the JSON documents "things/1" and all other
documents that are mentioned in it's x.Owner property. It doesn't care
about the type. The client API will do the conversion for you when you
deserialize (e.g. call Load and use that ID)
On Wed, May 2, 2012 at 10:24 PM, Chris Marisic <ch...@marisic.com> wrote:
> No I don't want to do a multiple level include, I'm exploring allowing 1
> type of document (Thing) to have multiple types of owners and from what
> Itamar said it should. Actually typing out code this should be the real
> usage correct?
> This almost seems wrong as I really want to get back a company or a person
> depending on Owner, but I see it's setup like this so i can properly use
> strongly typed access to reach x=>x.Owner of Thing, correct? That using
> less strong typing that it would be the same as:
> Session.Include("Owner").Load<Thing>("things/1"); correct?
> On Wednesday, May 2, 2012 3:15:52 PM UTC-4, Oren Eini wrote:
>> It sounds like you are trying to dO multi level include, is this what you
>> are doIng?
>> On Wednesday, May 2, 2012, Chris Marisic wrote: