Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We all know these fields, database admins so like to add:

  • UserCreated & DateCreated
  • UserUpdated & DateUpdated

They need to be displayed in the UI so I want to put them in some ValueObject but I can't come up with a good name to call the class...

share|improve this question

closed as primarily opinion-based by MichaelT, gnat, GlenH7, Kilian Foth, Robert Harvey Oct 14 '13 at 22:19

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

Something like UpdateInfo or CreateAndUpdateInfo? – 9000 Oct 2 '13 at 23:47
I was looking for something semantically meaningful but I'll go with CreateAndUpdateInfo, thanks :) – Laoujin Oct 3 '13 at 0:25
what if later you need to add more values, i propose you pick MetaInformations. – Kemoda Oct 3 '13 at 6:25
up vote 4 down vote accepted

Your DBA insists on these fields because he/she wants to ensure that the user and date of the last change is recorded. This sort of tracking is called audit, and the history of these changes is an audit trail.

So how about AuditInfo?

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.