title: LINQ to SQL and Concurrency Issues
body: <p>We are trying to build a High-Volume Orders Record System.
  There are three primary tables:
  1. Orders
  2. OrderDetails
  3. OrderShipment</p>
  
  <p>The Shipment table contains n record per order and any record shipment entry can be changed before the Customer accepts th order, after which it is frozen. (A business requirement)</p>
  
  <p>Although this may not happen in real world scenarios...
  during our load tests, we are getting System.Data.Linq.ChangeConflictException exceptions.
  Wrapping up the submit inside a transacion is not helping either.
  Can't we force LINQ to get a lock on the row for the entire duration of the update operation?</p>
  
  <p>Is there any other way to get over this?</p>