LINQ to SQL - Is it true that SubmitChanges() automatically starts a transaction?

When you call SubmitChanges, LINQ to SQL examines the set of known objects to determine whether new instances have been attached to them. If they have, these new instances are added to the set of tracked objects Immediately before any actual changes are transmitted LINQ to SQL starts a transaction to encapsulate the series of individual commands The changes to the objects are translated one by one to SQL commands and sent to the server At this point, any errors detected by the database cause the submission process to stop, and an exception is raised All changes to the database are rolled back as if no submissions ever occurred For more info on this view the MSDN article Hope this helps!

When you call SubmitChanges, LINQ to SQL examines the set of known objects to determine whether new instances have been attached to them. If they have, these new instances are added to the set of tracked objects. Immediately before any actual changes are transmitted, LINQ to SQL starts a transaction to encapsulate the series of individual commands.

The changes to the objects are translated one by one to SQL commands and sent to the server. At this point, any errors detected by the database cause the submission process to stop, and an exception is raised. All changes to the database are rolled back as if no submissions ever occurred.

For more info on this view the MSDN article. Hope this helps!

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.