DLINQ vs DataTable,TableAdapter, etc

Hello,

I may not understand DLINQ fully, but what are the advantages of it vs. just using a datatable, dataset etc Thank you!

Edited -Changed LINQ to DLINQ

Gerry Fan

Instead of using DataTables and DataSets you are using classes and collections and navigating relationships. For many people thinking of a Customer as a Customer Class as opposed to a row in a DataTable is far more intuitive. Getting a customer's orders would be represented as Customer.Orders as opposed to accessing child rows in a DataTable in a DataSet. You end up getting an object model that suggests nothing about the existence of a database, tables, SQL, queries, etc. Ideally, anyway. In the real world you never get that abstracted from persistent storage.

I think more people may naturally move to classes and collections if it weren't so time consuming and complicated to deal with what Dlinq hopes to solve - mapping objects and collections to database tables, tracking changes in objects, and updating the database appropriately based on changes made to business objects ( CRUD and Transactions ). DataSets have a lot of this built-in for free, but people who prefer classes and collections have to create this manually or deal with 3rd party products.

I hope this helps. I purposely avoided the topics of OOP and Object/Relational Mapping, which is the subject of many, many books.

Best Regards,

Dave
guptasameer1984
I've not played around with it myself but from my understanding the syntax and ability to manipulate is greatly improved and more intuitive (especially to those with prior sql background).
DLINQ vs DataTable,TableAdapter, etc