CODEWITHSUNDEEP
sqllinq
user366312
user366312

Reputation: 16894

LINQ syntax vs SQL syntax

Why did Andres Heilsberg designed LINQ syntax to be different than that of SQL (whereby made an overhead for the programmers to learn a whole new thing)?

Weren't it better if it used same syntax as of SQL?

Upvotes: 3

Views: 1462

Answers (4)

Dimas Rodriguez
Dimas Rodriguez

Reputation: 1

The reason is the C# language designers use this approach because of when I first specify where the data is coming from, now Visual Studio and the C# compiler know what my data looks like. And I can have IntelliSense help in the rest of the query because Visual Studio will know that "city" (for example) is a string, and it has operations like startsWith and a property named length. And really, inside of a relational database like SQL Server, the select clause that you are writing in a SQL statement at the top is really one of the last pieces of the information the query engine has to figure out. Before that it has to figure out what table you are working against in the from clause even though the from clause comes later in SQL syntax

Upvotes: 0

Jon Skeet
Jon Skeet

Reputation: 1499800

LINQ isn't meant to be SQL. It's meant to be a query language which is as independent of the data source as reasonably possible. Now admittedly it has a strong SQL bias, but it's not meant to just be embedding SQL in source code (fortunately).

Personally, I vastly prefer LINQ's syntax to SQL's. In particular, the ordering is much more logical in LINQ. Just by looking at the order of the query clauses, you can see the logical order in which the query is processed. You start with a data source, possibly do some filtering, ordering etc, and usually end with a projection or grouping. Compare that with SQL, where you start off saying which columns you're interested in, not even knowing what table you're talking about yet.

Not only is LINQ more logical in that respect, but it allows tools to work with you better - if Visual Studio knows what data you're starting with, then when you start writing a select clause (for example) it can help you with IntelliSense. Additionally, it allows the translation from LINQ query expressions into "dot notation" to be relatively simple using extension methods, without the compiler having to be aware of any details of what the query will actually do.

So from my point of view: no, LINQ would be a lot worse if it had slavishly followed SQL's syntax.

Upvotes: 22

Marc Gravell
Marc Gravell

Reputation: 1062510

First, choose your flavor of SQL - there are several! (T-, PL-, etc).

Ultimately, there are similarities and differences. A lot of the LINQ changes make more sense - i.e. choosing your source (FROM) before you try filtering (WHERE) / projection (SELECT), allowing better static analysis etc (including intellisense), and a more natural query comprehension syntax. This helps both the developer and the compiler, so I'm happy.

Upvotes: 5

elder_george
elder_george

Reputation: 7879

It is simpler to parse expression when initial data is provided in its beginning.

Because of this VS provides code completion even for partially written LINQ queries (great feature IMO).

Upvotes: 2

Related Questions