Does the LINQ syntax match the T-SQL order of execution? I suspect it does and thus the reason for the change in query order between SQL and LINQ but wanted some proof.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Does the LINQ syntax match the T-SQL order of execution? I suspect it does and thus the reason for the change in query order between SQL and LINQ but wanted some proof.
The reason queries are written in the form (from i in dc.table where …. select i) is for intellisense. It has to know what you’re working with before it can give you any good intellisense.
Similar to this question I think: https://stackoverflow.com/questions/1509106/why-didn't-the-linq-designers-stick-with-using-the-way-sql-is-written-today