To use LINQ to SQL or not ?
in [VB.NET]
|
From: Robbie on 13 Jun 2010 23:24 What are the pro and cons ?
From: Cor Ligthert[MVP] on 14 Jun 2010 01:31 Pro and cons against what, is better than ???? is worse than ???? This is a developer newsgroup you know, we want to be exact. "Robbie" <robc1(a)yahoo.com> wrote in message news:mradndVlrK12P4jRnZ2dnUVZ_rqdnZ2d(a)giganews.com... > What are the pro and cons ? > >
From: Mr. Arnold on 14 Jun 2010 01:32 Robbie wrote: > What are the pro and cons ? > > It's not about accessing SQL, which is just one aspect of using Linq. The pro is about this. The ability to use OOP(s) *objects*. The con to something like Linq-2-SQL is not understanding how to use Linq to query, which can create situations where access is slow in accessing a database, because one doesn't understand what type of T-SQL statements are generated based on the type of Linq query used. You may also want to look at ADO.NET Entity Framework, which is more powerful than Linq-2-SQL and uses Linq-2-Object. What is Object-oriented-programming? (OOP) is a programming paradigm that uses "objects" and their interactions to design applications and computer programs. The key concepts of OOP are the following: Class Object Instance Method Message passing Inheritance Abstraction Encapsulation Polymorphism Decoupling http://en.wikipedia.org/wiki/Object-oriented_programming What are design patterns? Design patterns are recurring solutions to software design problems you find again and again in real-world application development. Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges. http://www.developer.com/design/article.php/1502691 What is Object Relational Mapping? ORM) is a programming technique for converting data between incompatible type systems in relational databases and object-oriented programming languages. This creates, in effect, a "virtual object database," which can be used from within the programming language. There are both free and commercial packages available that perform object-relational mapping, although some programmers opt to create their own ORM tools. http://en.wikipedia.org/wiki/O-RM What is Language Integrated Query? LINQ is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages. Microsoft LINQ defines a set of query operators that can be used to query, project and filter data in arrays, enumerable classes, XML, relational database, and third party data sources. While it allows any data source to be queried, it requires that the data be encapsulated as objects. So, if the data source does not natively store data as objects, the data must be mapped to the object domain. Queries written using the query operators are executed either by the LINQ query processing engine or, via an extension mechanism, handed over to LINQ providers which either implement a separate query processing engine or translate to a different format to be executed on a separate data store (such as on a database server as SQL queries). The results of a query are returned as a collection of in-memory objects that can be enumerated using a standard iterator function such as C#'s foreach. Many of the concepts that LINQ has introduced were originally tested in Microsoft's C? research project. LINQ was released as a part of .NET Framework 3.5 on November 19, 2007. http://en.wikipedia.org/wiki/Language_Integrated_Query What is Linq-to-SQL? LINQ to SQL, a component of Visual Studio Code Name "Orcas", provides a run-time infrastructure for managing relational data as objects without losing the ability to query. It does this by translating language-integrated queries into SQL for execution by the database, and then translating the tabular results back into objects you define. Your application is then free to manipulate the objects while LINQ to SQL stays in the background tracking your changes automatically. http://msdn.microsoft.com/en-us/library/bb425822.aspx What is ADO.NET Entities framework? ADO.NET Entity Framework is an object-relational mapping (ORM) framework for the .NET Framework. This framework is Microsoft's first ORM offering for the .NET Framework. While Microsoft provided objects to manage the Object-relational impedance mismatch (such as a DataSet). ADO.NET Entity Framework is included with .NET Framework 3.5 Service Pack 1 and Visual Studio 2008 Service Pack 1, released on 11 Aug 2008. It also includes the capability of executing LINQ against ADO.NET Entity Framework entities http://en.wikipedia.org/wiki/ADO.NET_Entity_Framework
From: Robbie on 14 Jun 2010 06:19 Thank You very much ! "Mr. Arnold" <Arnold(a)Arnold.com> wrote in message news:emXPXM4CLHA.5584(a)TK2MSFTNGP06.phx.gbl... > Robbie wrote: >> What are the pro and cons ? > > It's not about accessing SQL, which is just one aspect of using Linq. The > pro is about this. The ability to use OOP(s) *objects*. > > The con to something like Linq-2-SQL is not understanding how to use Linq > to query, which can create situations where access is slow in accessing a > database, because one doesn't understand what type of T-SQL statements are > generated based on the type of Linq query used. > > You may also want to look at ADO.NET Entity Framework, which is more > powerful than Linq-2-SQL and uses Linq-2-Object. > > > What is Object-oriented-programming? > > (OOP) is a programming paradigm that uses "objects" and their interactions > to design applications and computer programs. > > The key concepts of OOP are the following: > Class > Object > Instance > Method > Message passing > Inheritance > Abstraction > Encapsulation > Polymorphism > Decoupling > > http://en.wikipedia.org/wiki/Object-oriented_programming > > > What are design patterns? > > Design patterns are recurring solutions to software design problems you > find again and again in real-world application development. Patterns are > about design and interaction of objects, as well as providing a > communication platform concerning elegant, reusable solutions to commonly > encountered programming challenges. > > http://www.developer.com/design/article.php/1502691 > > What is Object Relational Mapping? > > ORM) is a programming technique for converting data between incompatible > type systems in relational databases and object-oriented programming > languages. This creates, in effect, a "virtual object database," which can > be used from within the programming language. There are both free and > commercial packages available that perform object-relational mapping, > although some programmers opt to create their own ORM tools. > > http://en.wikipedia.org/wiki/O-RM > > What is Language Integrated Query? > > LINQ is a Microsoft .NET Framework component that adds native data > querying capabilities to .NET languages. > Microsoft LINQ defines a set of query operators that can be used to query, > project and filter data in arrays, enumerable classes, XML, relational > database, and third party data sources. While it allows any data source to > be queried, it requires that the data be encapsulated as objects. So, if > the data source does not natively store data as objects, the data must be > mapped to the object domain. Queries written using the query operators are > executed either by the LINQ query processing engine or, via an extension > mechanism, handed over to LINQ providers which either implement a separate > query processing engine or translate to a different format to be executed > on a separate data store (such as on a database server as SQL queries). > The results of a query are returned as a collection of in-memory objects > that can be enumerated using a standard iterator function such as C#'s > foreach. > Many of the concepts that LINQ has introduced were originally tested in > Microsoft's C? research project. LINQ was released as a part of .NET > Framework 3.5 on November 19, 2007. > > http://en.wikipedia.org/wiki/Language_Integrated_Query > > What is Linq-to-SQL? > > LINQ to SQL, a component of Visual Studio Code Name "Orcas", provides a > run-time infrastructure for managing relational data as objects without > losing the ability to query. It does this by translating > language-integrated queries into SQL for execution by the database, and > then translating the tabular results back into objects you define. Your > application is then free to manipulate the objects while LINQ to SQL stays > in the background tracking your changes automatically. > > http://msdn.microsoft.com/en-us/library/bb425822.aspx > > What is ADO.NET Entities framework? > > ADO.NET Entity Framework is an object-relational mapping (ORM) framework > for the .NET Framework. This framework is Microsoft's first ORM offering > for the .NET Framework. While Microsoft provided objects to manage the > Object-relational impedance mismatch (such as a DataSet). > ADO.NET Entity Framework is included with .NET Framework 3.5 Service Pack > 1 and Visual Studio 2008 Service Pack 1, released on 11 Aug 2008. It also > includes the capability of executing LINQ against ADO.NET Entity Framework > entities > > http://en.wikipedia.org/wiki/ADO.NET_Entity_Framework > >
|
Pages: 1 Prev: DGV doesnt display cells (what??) Next: something curious when compiling |