Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have a requirement similar to yours. In my case, it's a health care application and the audit log needs to identify the patient to which the insert/update applies.</p> <p>My solution is to define an interface, which all audited classes need to implement :</p> <pre><code>public interface IAuditedRecord { IPatient OwningPatient { get; } ... // Other audit-related properties (user, timestamp) } </code></pre> <p>The audited classes then implement this interface in whatever way is required. For example:</p> <pre><code>public class Medication : IAuditedRecord { // One end of a bidirectional association. Populated by NHibernate. private IPatient _patient; IPatient OwningPatient { get { return _patient; } } } public class MedicationNote : IAuditedRecord { // One end of a bidirectional association. Populated by NHibernate. private Medication _medication; IPatient OwningPatient { get { return _medication.OwningPatient; } } } </code></pre> <p>The <code>IPostInsertEventListener</code> and <code>IPostUpdateEventListener</code> then fetch the <code>OwningPatient</code> property in order to populate the audit record.</p> <p>The solution has the advantages of keeping the auditing logic in the event listeners, which is the only place where one is sure that an insert/update will take place, as well as allowing the traversal of indirect links between an object and its owning patient.</p> <p>The downside is that the audited classes have to derive from a specific interface. I think the benefits outweigh this small cost.</p>
    singulars
    1. This table or related slice is empty.
    1. POComplex NHibernate Auditing
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaul Lalonde
    1. USPaul Lalonde
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POComplex NHibernate Auditing
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COInteresting. I used a similar approach not long ago, except instead of a getter I had a setter on the IEntity interface, which each POCO implemented. I injected User on the constructor of the repository base class, and when a persist(IEntity poco) action was called on any repository class, it would call the setter on the persistent entity (we stored the last user to touch the record on the record itself). This allowed us to ignore event listeners altogether. The nice thing about your approach, however, is that you can pick and choose which classes should be audited.
      singulars
      1. PO
      1. USNelson
    2. COFunny, that's pretty much what I ended up doing. I defined an "EmployeeIdForAuditing" property (only getter) on our IDomainEntity, then had it return null in the base DomainEntity class. We also had a requirement to know whether each entry was an Employee/Company level "edit", so we created an audit attribute with the information. Any object that was an IDomainEntity and tagged with the Employee level audit attribute is required to implement the property. This also allowed me to write a test to check all the objects in our project for those requirements. Thanks for posting this!
      singulars
      1. PO
      1. USDarrell Mozingo
 

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