Using: LLBLGen 2.5 & SQL Server 2005

Most of our tables will have information such as create date and last modified date. For the create date, I have seen in the forums the suggestion to have a default value on the table which is inline with what we were planning. The question I have is for the modification date. What do you find as a best practice and convenience for getting the row's last modification date set appropriately?

What do you find as a best practice and convenience for getting the row's last modification date set appropriately?

I use Sql Server. With it, I like to use an update trigger.

if you want this in the business logic you can override the OnBeforeDelete method and check 1. if the entity IsNew 2. if the field exists

something like this

    public partial class DataAccessAdapter
    {
        protected override void OnBeforeEntitySave(IEntity2 entitySaved, bool insertAction)
        {
            if (entitySaved.Fields["UpdatedOn"] != null && !entitySaved.IsNew)
            {
                entitySaved.SetNewFieldValue("UpdatedOn", DateTime.Now);
            }
            base.OnBeforeEntitySave(entitySaved, insertAction);
        }
    }

Or use the new v2.5 AuditorClasses via Dependency Injection, so you can separate the audit logic and generalize it if you need to. For more info read LLBLGenPro(2.5) Help - Using generated code - Setting up and using Auditing

Auditing as it is build into v2.5 is designed to be a recorder for actions that were successfully completed.

You could use the set field audit action to log into the entity who changed what.