tag:blogger.com,1999:blog-464390995524552962.post4791769843055345744..comments2009-03-16T11:51:56.294-04:00Comments on I don't have time for this: Why LINQ is better than SQL (Part 1?)Daniel Pratthttp://www.blogger.com/profile/09623273077660656625noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-464390995524552962.post-10812123780824305722009-03-16T11:51:00.000-04:002009-03-16T11:51:00.000-04:00I think I figured it out, you have to start from t...I think I figured it out, you have to start from the highest part in the chain in order to drill down like that.iMehttp://www.blogger.com/profile/05054029415863355388noreply@blogger.comtag:blogger.com,1999:blog-464390995524552962.post-48780669388980920152009-03-16T11:39:00.000-04:002009-03-16T11:39:00.000-04:00are you sure your example works? I tried it and w...are you sure your example works? I tried it and when i hit dot on the table I'm referencing I can pull up the related tables but when I hit dot after that I don't see any column names, just functions relating to LINQ like "add", "addRange", "Aggregate<>", etc... From what I'm experiencing, I will have to do a join anyways, not the magic that you describe in your post. :PiMehttp://www.blogger.com/profile/05054029415863355388noreply@blogger.comtag:blogger.com,1999:blog-464390995524552962.post-57081938604488060612008-12-05T17:58:00.000-05:002008-12-05T17:58:00.000-05:00What you're really liking here is the ORM layer (e...What you're really liking here is the ORM layer (entity framework?) that's providing you the nice query abilities. LINQ is just the cherry on top of that.PSteelehttp://www.blogger.com/profile/14982870698703786068noreply@blogger.com