Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I assume that you also have a timestamp in the audit table.

    If you find yourself a lot of date-dependent data analysis queries against the audit table, you might find that it works better to adopt a scheme whereby a value for an item has an "effectivity range". That is, explicity record both start and stop datetimes for the validity of a value. (Any item that's currently effective would have a NULL stop time.) This makes it a lot easier to answer "what was the value for item on January 10th" questions.