Re: Auditing

From: Jared Still <>
Date: Wed, 4 Mar 2009 11:56:29 -0800
Message-ID: <>

This is a quite ridiculous request IMO.

Those asking for it are probably quite ignorant of the amount of time and effort required to do something like this.

My suggestion: estimate the cost of doing this (your time) and how it will impact other duties.

Also, has anyone, anywhere, ever seen an app with all these capabilities?

Personally I don't know of one, but adding these 'features' to any app would take a developer quite a bit of time, and it would be fairly expensive.

One more suggestion: consider how many times in the past 5 years any of these 'capabilities' have been needed.


On Wed, Mar 4, 2009 at 7:58 AM, Bill Ferguson <> wrote:

> Types of changes that must be reported:
> 1. Modifications of fields in an existing row
> 2. Deleted rows in subordinate tables (for example commodities_base)
> 3. Inserted rows in subordinate tables
> 4. Deleted records (rows in deposits_base table)
> 5. Inserted records
> 6. Schema changes (added or removed fields or tables)
> Information to be reported about each change (numbers match numbers above):
> 1. date, time, userid, dep_id, table,{field, old value, new value},
> {field, old, new}, ...
> 2. date, time, userid, dep_id, table,{old field values}
> 3. date, time, userid, dep_id, table,{new field values}
> 4. date, time, userid, dep_id, a complete copy of the existing record
> at time of deletion (possibly in XML)
> 5. date, time, userid, new dep_id
> 6. date, time, userid, table,[field],description of change
> Ways in which this information must be available:
> by time interval
> by userid
> for dep_id
> for table
> for field within table
> The user interface must allow any or all of these to be specified to
> present a list of changes in its report.

Received on Wed Mar 04 2009 - 13:56:29 CST

Original text of this message