This topic is locked

Auditing - Suggestion

8/31/2010 10:50:46 AM
PHPRunner General questions
K
kenlyle author

I don't think that the current text field with the Old/New is as useful as it could be. I think that probably old and new should be fields in the database with just the value. Maybe this could be a configuration option, "Store audited values as separate fields".
The issue is that I want to be able to do "retrospectives", i.e. what was the state of the database at a certain point in time? To be even more clear, I would like to query "What was the state of the database on July 1, 2010?". The objective will actually be- What did we expect to happen as of July 1, and how does that compare with the next round of updates?" Formulating those queries might be a little tricky, but we can deal with that once this suggestion is implemented.
OK, I think this is pretty obvious and minor, because you obviously already have the trigger for on update.
Thanks for this feature as it currently exists, BTW.

K
kenlyle author 9/4/2010

As always, I got a quick response from Support: "PHPRunner 5.3 will have 'Before audit' event which allows you to customize what's being logged."
Could I get some more specifics about how this would be coded, specifically, to save the before and after values as separate fields, so that they can be queried directly?
Thanks,

K