Databases
StackOverflow2013
Postsdbo
POExtend base type and automatically update audit information on Entity
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExtend base type and automatically update audit information on Entity
    primarykey
    data
    text
    <p>I have an entity model that has audit information on every table (50+ tables)</p> <pre><code> CreateDate CreateUser UpdateDate UpdateUser </code></pre> <p>Currently we are programatically updating audit information. </p> <p>Ex: </p> <pre><code> if(changed){ entity.UpdatedOn = DateTime.Now; entity.UpdatedBy = Environment.UserName; context.SaveChanges(); } </code></pre> <p>But I am looking for a more automated solution. During save changes, if an entity is created/updated I would like to automatically update these fields before sending them to the database for storage. </p> <p>Any suggestion on how i could do this? I would prefer to not do any reflection, so using a text template is not out of the question.</p> <p>A solution has been proposed to override SaveChanges and do it there, but in order to achieve this i would either have to use reflection (in which I don't want to do ) or derive a base class. Assuming i go down this route how would I achieve this? </p> <p>For example</p> <pre><code>EXAMPLE_DB_TABLE CODE NAME --Audit Tables CREATE_DATE CREATE_USER UPDATE_DATE UPDATE_USER </code></pre> <p>And if i create a base class </p> <pre><code> public abstract class IUpdatable{ public virtual DateTime CreateDate {set;} public virtual string CreateUser { set;} public virtual DateTime UpdateDate { set;} public virtual string UpdateUser { set;} } </code></pre> <p>The end goal is to be able to do something like...</p> <pre><code> public overrride void SaveChanges(){ //Go through state manager and update audit infromation //FOREACH changed entity in state manager if(entity is IUpdatable){ //If state is created... update create audit. //if state is updated... update update audit } } </code></pre> <p>But I am not sure how I go about generating the code that would extend the interface.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNix
    1. USNix
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POExtend base type and automatically update audit information on Entity
      1. USNix
      1. VTBountyStart
    2. VO
      singulars
      1. POExtend base type and automatically update audit information on Entity
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POExtend base type and automatically update audit information on Entity
      1. USDerek
      1. VTFavorite
    1. COThis isn't really a direct answer, but I've done something similar with LINQ to SQL. Check out my blog post http://farm-fresh-code.blogspot.com/2009/05/auditing-inserts-and-updates-using-linq.html. It might give you some ideas. The basic idea is to extend the data context and override SubmitChanges and do the audit work there. My audit information is stored in a different table and I audit both success and failure so it uses a separate context, but you may still get some ideas from it.
      singulars
      1. POExtend base type and automatically update audit information on Entity
      1. UStvanfosson
    2. COThanks. I was looking into doing some code gen stuff using .tt files, but i was hoping for something simpler, ill read it tonight and get back to you.
      singulars
      1. POExtend base type and automatically update audit information on Entity
      1. USNix
 

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