LINQ to SQL produces incorrect TSQL when using UNION or CONCAT - by George Tsiokos

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


17
0
Sign in
to vote
ID 355734 Comments
Status Closed Workarounds
Type Bug Repros 11
Opened 7/10/2008 10:48:37 AM
Access Restriction Public

Description

When a LINQ to SQL query contains a Union or Concat with a second query, and the second query references a column twice, a SqlException will occur.
Sign in to post a comment.
Posted by kainhart on 7/23/2009 at 5:25 AM
This is also an issue with computed values such as multiple nulls or any value type literal that is repeated within the projection. This is a serious problem and there are several people who are blocked because of this.
Posted by Microsoft on 2/25/2009 at 4:39 PM
Hi,

Thank you for taking the time to send this feedback and bug report. We have reviewed the issue and confirmed the behavior, but we will not be fixing this in the next release of LINQ to SQL.

LINQ to SQL Team
Posted by Microsoft on 7/10/2008 at 11:17 PM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team