Databases
StackOverflow2013
Postsdbo
POOptimizing Repository’s SubmitChanges Method
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOptimizing Repository’s SubmitChanges Method
    primarykey
    data
    text
    <p>I have following repository. I have a mapping between LINQ 2 SQL generated classes and domain objects using a factory. </p> <p>The following code will work; but I am seeing two potential issues</p> <p>1) It is using a SELECT query before update statement.</p> <p>2) It need to update all the columns (not only the changed column). This is because we don’t know what all columns got changed in the domain object.</p> <p>How to overcome these shortcomings?</p> <p>Note: There can be scenarios (like triggers) which gets executed based on specific column update. So I cannot update a column unnecessarily. </p> <p><strong>REFERENCE</strong>:</p> <ol> <li><p><a href="https://stackoverflow.com/questions/11189688/linq-to-sql-updating-without-refresh-when-updatecheck-never">LINQ to SQL: Updating without Refresh when “UpdateCheck = Never”</a></p></li> <li><p><a href="http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=113917" rel="nofollow noreferrer">http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=113917</a></p></li> </ol> <p><strong>CODE</strong></p> <pre><code>namespace RepositoryLayer { public interface ILijosBankRepository { void SubmitChangesForEntity(); } public class LijosSimpleBankRepository : ILijosBankRepository { private IBankAccountFactory bankFactory = new MySimpleBankAccountFactory(); public System.Data.Linq.DataContext Context { get; set; } public virtual void SubmitChangesForEntity(DomainEntitiesForBank.IBankAccount iBankAcc) { //Does not get help from automated change tracking (due to mapping) //Selecting the required entity DBML_Project.BankAccount tableEntity = Context.GetTable&lt;DBML_Project.BankAccount&gt;().SingleOrDefault(p =&gt; p.BankAccountID == iBankAcc.BankAccountID); if (tableEntity != null) { //Setting all the values to updates (except primary key) tableEntity.Status = iBankAcc.AccountStatus; //Type Checking if (iBankAcc is DomainEntitiesForBank.FixedBankAccount) { tableEntity.AccountType = "Fixed"; } if (iBankAcc is DomainEntitiesForBank.SavingsBankAccount) { tableEntity.AccountType = "Savings"; } Context.SubmitChanges(); } } } } namespace DomainEntitiesForBank { public interface IBankAccount { int BankAccountID { get; set; } double Balance { get; set; } string AccountStatus { get; set; } void FreezeAccount(); } public class FixedBankAccount : IBankAccount { public int BankAccountID { get; set; } public string AccountStatus { get; set; } public double Balance { get; set; } public void FreezeAccount() { AccountStatus = "Frozen"; } } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USLijo
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOptimizing Repository’s SubmitChanges Method
      1. USLijo
      1. VTFavorite
    2. VO
      singulars
      1. POOptimizing Repository’s SubmitChanges Method
      1. USChris Moutray
      1. VTFavorite
    1. CO"It need to update all the column". What exactly is the performance hit of this? Have you measured this?
      singulars
      1. POOptimizing Repository’s SubmitChanges Method
      1. USSteven
    2. CO@Steven It was my assumption. After all, it is an unwanted effort -logically. May not be true from SQL perspective. Also, there can be scenarios (like triggers) which gets executed based on column update. So I cannot update a column unnecessarily. http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=113917
      singulars
      1. POOptimizing Repository’s SubmitChanges Method
      1. USLijo
    3. COUnless you "inherited" the database design, I think you really have to reconsider this use of triggers. If you need to trigger just because the record changes, use a timestamp in the table and have your update triggers respond to that.
      singulars
      1. POOptimizing Repository’s SubmitChanges Method
      1. USPleun
 

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