Databases
StackOverflow2013
Postsdbo
POUnit of Work pattern vs. Transaction Scope for Linq-To-Sql?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnit of Work pattern vs. Transaction Scope for Linq-To-Sql?
    primarykey
    data
    text
    <p>I would like to mimic the Repository approach that is widely used in DDD with Linq-2-Sql in my portal app. So far I have this: </p> <pre><code> public class LinqToSqlDal&lt;DC,T&gt;: IDisposable, IRepository&lt;T&gt; where T: LinqEntity, new(), where DC: DataContext, new() { private DC unitOfWork = null; public LinqToSqlDal(string connectionString) { this.unitOfWork = Activator.CreateInstance(typeof(DC), connectionString) as DC; } public LinqToSqlDal(string connectionString, DataLoadOptions loadOptions): this(connectionString) { this.unitOfWork.LoadOptions = loadOptions; } public virtual void SubmitChanges() { this.unitOfWork.SubmitChanges(); } public virtual List&lt;T&gt; Get(Expression&lt;Func&lt;T,bool&gt;&gt; query) { return this.unitOfWork.GetTable&lt;T&gt;().Where(query); } public virtual void Delete(Expression&lt;Funct&lt;T, bool&gt;&gt; query) { this.unitOfWork.GetTable&lt;T&gt;().DeleteAllOnSubmit(this.unitOfWork.GetTable&lt;T&gt;().Where(query)); } public virtual T GetByID&lt;T&gt;(Expression&lt;Funct&lt;T, bool&gt;&gt; query) { return this.unitOfWork.GetTable&lt;T&gt;().Where(query).SingleOrDefault(); } public virtual object Add(T entity, string IDPropertyName) { this.unitOfWork.GetTable&lt;T&gt;().InsertOnSubmit(entity); this.SubmitChanges(); var ID = (string.IsNullOrEmpty(IDPropertyName)) ? null : entity.GetType().GetProperty(IDPropertyName).GetValue(entity, null); return ID; } public virtual void SubmitChanges() { this.unitOfWork.SubmitChanges(); } public void Dispose() { this.unitOfWork.Dispose(); } } </code></pre> <p>So now I can use this with any Entity and DataContext that entity belongs to. My question is - would passing or instantiating a TransactionScope inside this little repository benefit? So far I have only one DataContext but can have multiple going forward, what can be done to the current design to ensure transactions across multiple data contexts?</p> <p>Is this a good approach to wrap the context with using generics and let the clients dispose of it?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdexter
    1. USdexter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUnit of Work pattern vs. Transaction Scope for Linq-To-Sql?
      1. USmatt
      1. VTFavorite
    2. VO
      singulars
      1. POUnit of Work pattern vs. Transaction Scope for Linq-To-Sql?
      1. USNathan
      1. VTFavorite
    3. VO
      singulars
      1. POUnit of Work pattern vs. Transaction Scope for Linq-To-Sql?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload