> > Your example however has an interesting problem. What if a customer
> > has 2 relationships with Address: visitor and billing address?
>
> In that case, we specify which attribute in the Customer
> object is the "graft point". Ala:
> customerQuery.AddJoin(Customers.Attributes.ShipAddress,
> Address);
> We also can supply aliases to support multiple joins to the
> same table.
ok, sounds good, though it requires join information to be known
by the developer, which was what some people argued against. (but is
inevitable to be there, IMHO)
FB
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
Some .NET courses you may be interested in:
NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles
http://www.develop.com/courses/gaspdotnetls
View archives and manage your subscription(s) at http://discuss.develop.com
