The application can manipulate the objects while LINQ to SQL stays in the background, tracking changes to the data automatically.
LINQ does not aim to circumvent a data abstraction layer at the database level, based on stored procedures; in fact it makes their use easier for the programmer.
People have been asking via Twitter and the LINQ to SQL forums so here’s a list I put together on a number of the changes made for 4.0.
– Updated with additional changes, some of which are new in beta 2.
This makes more sense and means your app would break on the first page now instead of subtlety breaking on the second page.Almost all current Programming languages model their data in terms of objects while the relational databases use entities and relationships for the same purpose.LINQ to SQL is the first stage of LINQ technology, the aim of which is to bridge the gap between the two different ways of representing data entities.We worked very hard to avoid breaking changes but of course any potential bug fix is a breaking change if your application was depending on the wrong behavior.The ones I specifically want to call out are: The special-casing of 0 for Skip to be a no-op was causing some subtle issues such as eager loading to fail and we took the decision to stop special casing this.