> though it requires join information to be known > by the developer, which was what some people argued > against.
But only when there are multiple paths to the destination table. In the general FK relationship, that happens some; but in the parent-child it never does, so that does simplify a lot of code. There's no substitute for knowing the problem domain, and there's very little substitute for making things easier for the "average" developer. Once they find one of these ambiguous queries, suddenly they NEED to know the relationships, so they learn them. But until they need it, they don't have to worry about it. > (but is inevitable to be there, IMHO) When it's not unambiguous, it's got to be disambiguated ;) Marc =================================== 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
