Data auditing is a required internal control for many business systems (see Sarbanes Oxley for reasons why). It must be at the database level to assure that all changes are captured especially unauthorized ones.
These fields can be automated updated by service layer and these fields may not be rendered on the screen, unless selected as explicit option while generating the entity
Motivation for or Use Case
These columns are for the benefit of the DBA and the database developers. They just provide a quick mechanism to answer questions like "When did this record last change?" "who changed it?" They are not robust enough or fine-grained enough to satisfy compliance with SOX, HIPAA or whatever.
Related issues or PR
[Y] Checking this box is mandatory (this is just to show you read everything)
Overview of the feature request
Create Audit Fields as explained below
Data auditing is a required internal control for many business systems (see Sarbanes Oxley for reasons why). It must be at the database level to assure that all changes are captured especially unauthorized ones.
These fields can be automated updated by service layer and these fields may not be rendered on the screen, unless selected as explicit option while generating the entity
Motivation for or Use Case
These columns are for the benefit of the DBA and the database developers. They just provide a quick mechanism to answer questions like "When did this record last change?" "who changed it?" They are not robust enough or fine-grained enough to satisfy compliance with SOX, HIPAA or whatever.
Related issues or PR