Home Dashboard Directory Help
Search

LINQ generated classes cannot handle stored procedures that produce a result table with an unnamed column by HugoDeVreugd


Status: 

Closed
 as Fixed Help for as Fixed


0
0
Sign in
to vote
Type: Bug
ID: 325423
Opened: 1/31/2008 12:48:54 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

If a database contains a stored procedure that uses a select statement with an unnamed column, then the generated LINQ function does not return the resulting value of the select statement.

The same stored procedure with a named column in the select does produce the right result using LINQ.

BTW: the same issue occurs in C#
Details
Sign in to post a comment.
Posted by Microsoft on 3/7/2009 at 11:29 PM
Thanks for reporting this issue. This should be fixed in the next release of Visual Studio.

Data Programmability Tools Team
Posted by HugoDeVreugd on 2/6/2008 at 11:14 PM
I know the column isn't named, that's the whole point.
When you read my description in "Actual Results" it says: "the unnamed version has a property called Column1".
So, Linq generates a default column name: Column1. And ofcourse, Linq should have put the value of the unnamed column in this generated column.
Posted by Microsoft on 1/31/2008 at 9:23 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 1/31/2008 at 9:23 PM
Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Posted by David A Nelson on 1/31/2008 at 7:24 AM
If you haven't named the column, how do you expect LINQ to know what to return? Do you want it to read your mind?
Sign in to post a workaround.