Is it possible to set up a prefetch path for adapter that can span more than one relation(unless its m:n)?

Lets say I have 3 tables, contact , address and an area lookup (related m:1 and 1:n). I can set up a prefetch to retrieve address entities for each contact simply enough, but would like to avoid having to iterate over the addresses fetching the lookup tables. Being able to do this would be useful in lots of cicumstances - especialy for report datasets where I need to fetch a complete graph 'just in case'.

Ryan

ryanroberts wrote:

Is it possible to set up a prefetch path for adapter that can span more than one relation(unless its m:n)?

Lets say I have 3 tables, contact , address and an area lookup (related m:1 and 1:n). I can set up a prefetch to retrieve address entities for each contact simply enough, but would like to avoid having to iterate over the addresses fetching the lookup tables. Being able to do this would be useful in lots of cicumstances - especialy for report datasets where I need to fetch a complete graph 'just in case'. Ryan

You can setup ANY graph using prefetch paths.

I'll illustrate adapter here, selfservicing uses the variants with the '2'

PrefetchPath2 path = new PrefetchPath2((int)EntityType.ContactEntity); path.Add(ContactEntity.PrefetchPathAddress).SubPath.Add(AddressEntity.PrefetchPathAreaLookup);

et voila

Aha, SubPath! Should pay more attention to intellisense

Marvelous stuff Frans. If I could take this oppertunity to request features for your next release - the ability to map child entity collections to their parent in the same manner as fields would be handy.

Ryan

ryanroberts wrote:

Aha, SubPath! Should pay more attention to intellisense

Marvelous stuff Frans. If I could take this oppertunity to request features for your next release - the ability to map child entity collections to their parent in the same manner as fields would be handy.

Ryan

Do you have an example for that?

Otis wrote:

You can setup ANY graph using prefetch paths.

I'll illustrate adapter here, selfservicing uses the variants with the '2'

PrefetchPath2 path = new PrefetchPath2((int)EntityType.ContactEntity); path.Add(ContactEntity.PrefetchPathAddress).SubPath.Add(AddressEntity.PrefetchPathAreaLookup);

et voila

This was exactly what I was looking for! I think I'm in love....with the software of course.

NickD wrote:

Otis wrote:

You can setup ANY graph using prefetch paths.

I'll illustrate adapter here, selfservicing uses the variants with the '2'

PrefetchPath2 path = new PrefetchPath2((int)EntityType.ContactEntity); path.Add(ContactEntity.PrefetchPathAddress).SubPath.Add(AddressEntity.PrefetchPathAreaLookup);

et voila

This was exactly what I was looking for! I think I'm in love....with the software of course.

Heh yeah it sometimes has that effect on people