Bug or Feature: Stored Procedure that return Multiple Rows with same Primary Key value
During developing an application with LINQ to SQL, I found that when a stored procedure returns multiple distinct rows with same primary key then LINQ will make the complete list object same. For example, If I have the following table,

    ID  Name  Salary
    --  ----  -----
     1    A     20
     2    B     200
     3    C     30
     4    D     520

and my stored procedure returns all rows except with same primary key,

    ID  Name  Salary
    --  ----  -----
     1    A     20
     1    B     200
     1    C     30
     1    D     520

then  linq will bind these rows as,


    ID  Name  Salary
    --  ----  -----
     1    A     20
     1    A     20
     1    A     20
     1    A     20

Bug or Feature: Stored Procedure that return Multiple Rows with same Primary Key value
===

During developing an application with LINQ to SQL, I found that when a stored procedure returns multiple distinct rows with same primary key then LINQ will make the complete list object same. For example, If I have the following table,

    ID  Name  Salary
    --  ----  -----
     1    A     20
     2    B     200
     3    C     30
     4    D     520

and my stored procedure returns all rows except with same primary key,

    ID  Name  Salary
    --  ----  -----
     1    A     20
     1    B     200
     1    C     30
     1    D     520

then  linq will bind these rows as,


    ID  Name  Salary
    --  ----  -----
     1    A     20
     1    A     20
     1    A     20
     1    A     20
