Comments on: LINQ to SQL vs the Entity Framework http://freekleemhuis.com/2008/03/10/linq-stuff-part-1/ SoftWear 'n Tears Mon, 24 Oct 2011 20:02:18 +0000 hourly 1 http://wordpress.com/ By: Freek Leemhuis http://freekleemhuis.com/2008/03/10/linq-stuff-part-1/#comment-37 Mon, 26 May 2008 11:31:24 +0000 http://freekleemhuis.wordpress.com/?p=6#comment-37 Hi Wiebe,
True, if you have additional attributes that you want to model in the relationship, then you can regard it as an entity and it should then be mapped to a separate data class. However, in the example no such attributes were present and so there is no ‘entity’.

]]> By: Wiebe http://freekleemhuis.com/2008/03/10/linq-stuff-part-1/#comment-36 Mon, 26 May 2008 11:16:23 +0000 http://freekleemhuis.wordpress.com/?p=6#comment-36 Hi Freek,

In many situations you will also want to be able to describe the relationship between two entities, for example what role does this person fulfill within the company?

In that case the CompanyPerson entity is not that yuk :)

Wiebe

]]> By: LINQ to SQL problems « Freekshow http://freekleemhuis.com/2008/03/10/linq-stuff-part-1/#comment-16 Wed, 26 Mar 2008 16:51:55 +0000 http://freekleemhuis.wordpress.com/?p=6#comment-16 [...] sure you’re aware of the limited support LINQ to SQL has for eager loading  See my earlier post for more details on the differences between the Entity Framework and LINQ to [...]

]]>