Channel 9 Forums - Coffeehouse - Full Joins in Linq http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png Channel 9 Forums - Coffeehouse - Full Joins in Linq http://channel9.msdn.com/Forums Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them. http://channel9.msdn.com/Forums en Mon, 20 May 2013 09:00:33 GMT Mon, 20 May 2013 09:00:33 GMT Rev9 2 -2 -1 Coffeehouse - Full Joins in Linq In my humble in opinion, Linq needs better outer join support.  See this stackoverflow thread on how to perform a full join.

Do I stand alone?  Does anyone else find this very limiting?

Nowadays I pretty much use LinqPad and only SSMS and SQL when I have to.  Linq is definitely not an improvement with outer joins.  For most everything else I do, Linq is more efficient to develop.

 

MD

]]> http://channel9.msdn.com/Forums/Coffeehouse/Full-Joins-in-Linq/66bf759dd7f64ca78e35a0110123a513#66bf759dd7f64ca78e35a0110123a513 Sun, 11 Mar 2012 17:41:50 GMT http://channel9.msdn.com/Forums/Coffeehouse/Full-Joins-in-Linq/66bf759dd7f64ca78e35a0110123a513#66bf759dd7f64ca78e35a0110123a513 spottedmah 2 http://channel9.msdn.com/Niners/spottedmah/Discussions/RSS Coffeehouse - Full Joins in Linq That's kind of crazy, how can something so simple be so complicated?

something like this:

select * from a full outer join b on a.id = b.id

turns into a wall of seemingly impenetrable logic.

Would the zip extension method work for this?

]]> http://channel9.msdn.com/Forums/Coffeehouse/Full-Joins-in-Linq/e3c83f0289de4976bc83a0120027766f#e3c83f0289de4976bc83a0120027766f Mon, 12 Mar 2012 02:23:40 GMT http://channel9.msdn.com/Forums/Coffeehouse/Full-Joins-in-Linq/e3c83f0289de4976bc83a0120027766f#e3c83f0289de4976bc83a0120027766f Joshua Ross 2 http://channel9.msdn.com/Niners/Jsoh/Discussions/RSS