Hi,

With LLBLGen adapter, 5.8.1. If I retrieve the graph

A--with path to -B - with path to- C
   \with path to -D

And C also has a fk to D, where D is the parent. When using the FastSerializer with the DataScope, how should I go about recreating the graph on the client so that I can do D.C ? There's nothing built in to do this I suppose? I'm coming from RiaServices where this happened automatically as part of deserializing on the client.
I can do it manually by knowing on the client what the prefetch was on the server and recreating the missing links based on the keys, but wondered if the DataScope, as it knows about all the retrieved entities, could help?

Thanks

Hi yowl,

I'm not sure I understand clearly...

• Could you please show an example of how would you fetch such graph in the DataScope?
• AFAIK, FastSerialization works on Entities, TypedLists, TypedViews and UnitOfWork2 objects, not DataScope. Would you plan to transfer DataScope over remoting or something like that?

I think if you add a prefetch path node for D.C in the graph as well and fetch it with a context, the same C instances are referenced by D as are referenced by B. The fast serializer will rebuild this graph when deserializing.

Hi,

The prefetch would look like this:

(from a in meta.A
                    select a)
                                      .WithPath(ap => ap.Prefetch<BEntity>(aa => aa.B).SubPath(bp => bp.Prefetch(bb => bb.C))
                                      .Prefetch(ap => ap.D)

Yes, I suppose I could prefetch C again from D, although that would mean selecting the C entities twice. But that does make me think that I could do the linking on the server before serialization which would at least be better than doing it on the client as I wouldn't be duplicating the knowledge of the prefetch path to the client.

If you can enumerate the C instances to assign them to D's on the server, then sure, that should work out fine. As the FK values are fetched, they won't change by the assignments.

Got it, thanks.