Should I bother learning LinQ to Sql?

[Rich P]

From what I understand - the big deal with LinQ is that you can pull
data into your local app and query it within the local app using LinQ
and lambdas... and that you can debug LinQ like regular code where you
can't do that with TSql - Do I have this straight? So was LinQ
supposed to be supersceding TSql (plSql)? If not - what is the big deal
with LinQ

I have also been reading that LinQ is on its way out in place of some
other .Net thing (or Subsonice). Where should I place my focus for
interfacing between SqlServer (2005 and higher) and my local winform and
Web apps? I am guessing that if you can pull data into a web app onto a
local client and query it within the client without having to make
additional trips to the server this would be a benefit that LinQ brings
forth.

I would be grateful if someone could set me straight on the purose of
LinQ - or similar technology - and where I should put my energy.

Rich

 

[HillBilly]

Here it is in a nutshell; LINQ is a general purpose query language which
derives from T-SQL but is not neccessarily only used for relational data in
tables. While the LINQ to SQL --implementation-- will continue to be
supported you have correctly observed that future emphasis will be LINQ to
Entities supporting the Entity Framework. You'll also observe LINQ to XML is
being widely used as well as LUNQ to Objects and so on. Why?

Again, because LINQ was created to function as a generalized query grammar
we can reuse with all types of queries. So where you are at right now is
confusing implementation with the objective where as the objective was the
development of a single all-purpose query grammar.

As I have come to understand it.

 

[Arne Vajhøj]

From what I understand - the big deal with LinQ is that you can pull
data into your local app and query it within the local app using LinQ
and lambdas... and that you can debug LinQ like regular code where you
can't do that with TSql - Do I have this straight? So was LinQ
supposed to be supersceding TSql (plSql)?

Not really.

LINQ is a general query language embedded in the .NET languages C#
and VB.NET.

Two of the flavors LINQ to SQL and LINQ to EF goes to databases
(LINQ to XML goes to XML files and LINQ to Objects goes to in memory
data structures).

But LINQ to SQL and LINQ to EF are ORM style and does not replace
SQL for all purposes.

If not - what is the big deal
with LinQ

It is new and cool. And it is elegant to some things.

I have also been reading that LinQ is on its way out in place of some
other .Net thing (or Subsonice).

LINQ to EF are somewhat replacing LINQ to SQL.

Where should I place my focus for
interfacing between SqlServer (2005 and higher) and my local winform and
Web apps?

LINQ to EF.

Arne

 

[Arne Vajhøj]

Here it is in a nutshell; LINQ is a general purpose query language which
derives from T-SQL but is not neccessarily only used for relational data
in tables.

I don't think you can say that LINQ is derived from T-SQL.

Different paradigms.

And LINQ is more similar to earlier ORM QL than to real SQL.

Arne

 

[HillBilly]

The SELECT FROM WHERE grammar used by LINQ is distinctly SQL but the point
is not to quibble the point is to understand that Microsofrt designed LINQ
for the reason they said they designed LINQ and the reason they stated they
designed LINQ is to allow developers to have a general query language.

 

[Arne Vajhøj]

The SELECT FROM WHERE grammar used by LINQ is distinctly SQL but the
point is not to quibble the point is to understand that Microsofrt
designed LINQ for the reason they said they designed LINQ and the reason
they stated they designed LINQ is to allow developers to have a general
query language.

You can not conclude that any query syntax that uses SELECT, FROM
and WHERE is derived from T-SQL.

Those predates T-SQL with a decade or so.

If you had said SQL, then it would have been another story.

Arne

 

[varun.wipro]

From what I understand - the big deal with LinQ is that you can pull
data into your local app and query it within the local app using LinQ
and lambdas... and that you can debug LinQ like regular code where you
can't do that with TSql -  Do I have this straight?  So was LinQ
supposed to be supersceding TSql (plSql)? If not - what is the big deal
with LinQ

I have also been reading that LinQ is on its way out in place of some
other .Net thing (or Subsonice).  Where should I place my focus for
interfacing between SqlServer (2005 and higher) and my local winform and
Web apps?  I am guessing that if you can pull data into a web app onto a
local client and query it within the client without having to make
additional trips to the server this would be a benefit that LinQ brings
forth.  

I would be grateful if someone could set me straight on the purose of
LinQ - or similar technology - and where I should put my energy.

Rich

*** Sent via Developersdexhttp://www.developersdex.com***

Well i would say that the old conventional way is changing bcoz of
Entity
Framework and moreover it is quite efficient. Some of the things that
are
still under developement in EF but now or later EF would be a big
thing in
the market.

 

[Mr. Arnold]

I am guessing that if you can pull data into a web app onto a
local client and query it within the client without having to make
additional trips to the server this would be a benefit that LinQ brings
forth.

You can do this right now with .NET Entity Framework by use of an ASP.NET
Data service or Windows Communication Foundation Web Service via a Linq
query, with SQL Server on the backend. In other words, you can query the
database through the Web service from the client using Linq and EF and pull
the data to the client, called a Linq service provider.


__________ Information from ESET NOD32 Antivirus, version of virus signature database 4235 (20090711) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[Rich P]

Thanks all for your replies.

Rich