On Sat, Apr 12, 2014 at 2:57 AM, Tony Theodore wrote:
>
> I know this is a terribly old thread, but if you are still looking for
>> software to provide an audit trail of changes in the database, please see
>> Cyan Audit at http://pgxn.org/dist/cyanaudit. I think it will do just
>> what you're loo
On 12 April 2014 07:02, Moshe Jacobson wrote:
>
> I know this is a terribly old thread, but if you are still looking for
> software to provide an audit trail of changes in the database, please see
> Cyan Audit at http://pgxn.org/dist/cyanaudit. I think it will do just what
> you're looking for.
I know this is a terribly old thread, but if you are still looking for
software to provide an audit trail of changes in the database, please see
Cyan Audit at http://pgxn.org/dist/cyanaudit. I think it will do just what
you're looking for.
(Full disclosure: I am the author of this software)
Moshe
>For several reasons (including operational and legal) once data are
> entered in a table they cannot be changed or deleted without an audit
> trail of the change, when it occurred, who made the change, and the
> reason for it.
Besides the need for storing additional information that the user
In Java world, for this purpose I tend to use JPA/Hibernate with Envers
http://www.jboss.org/envers - db vendor agnostic solution.
Kind regards,
Stevo Slavic.
On Tue, Jan 8, 2013 at 6:32 AM, Craig Ringer wrote:
> On 4/01/2013 12:09 AM, Adrian Klaver wrote:
> > On 01/03/2013 07:38 AM, Rich Shep
On 4/01/2013 12:09 AM, Adrian Klaver wrote:
> On 01/03/2013 07:38 AM, Rich Shepard wrote:
>
>>
>>The middleware of the application needs to check this table when data
>> are
>> to be viewed in the UI and present only the current row contents. A
>> separate
>> view would display a history of cha
Hi again,
> I understand it and for this reason I said to "use some strategy to purge
> old historical data *OR* make your audit tables partitioned"...
yes, prepare to scale up in any case, even if it seems to be a remote
chance ATM. If the "untouched" nature of this data is so critical, you
have
On Thu, Jan 3, 2013 at 2:50 PM, Rich Shepard
wrote:
>
> There should not be many changes in these tables.
Ok.
>
> And historical data
> cannot be purged or the purpose of maintaining a history is lost. The
> history is valuable for tracking changes over time in regulatory agency
> staff and to
On Thu, 3 Jan 2013, Bèrto ëd Sèra wrote:
if it's a strict legal requirement you may want to enforce it with a
trigger system, so that each time a record is inserted/updated/deleted
you create an exact copy of it in a historical table, that has the
original record plus data about who performed th
Hi Rich,
if it's a strict legal requirement you may want to enforce it with a
trigger system, so that each time a record is inserted/updated/deleted
you create an exact copy of it in a historical table, that has the
original record plus data about who performed the operation, when,
from which IP,
On Thu, 3 Jan 2013, Adrian Klaver wrote:
As a matter of course I include fields to record the timestamp and user for
insert of records and last update of record on my tables.
Adrian,
This is a useful addition to the application.
For a relatively simple solution see this blog post I put up
On Thu, 3 Jan 2013, Fabrízio de Royes Mello wrote:
And keep in mind that kind of table tend to grow quickly, so you must use
some strategy to purge old historical data or make your audit table
partitioned...
Fabrizio,
There should not be many changes in these tables. And historical data
can
On Thu, Jan 3, 2013 at 2:09 PM, Adrian Klaver
wrote:
>
> On 01/03/2013 07:38 AM, Rich Shepard wrote:
>
>>The middleware of the application needs to check this table when data
>> are
>> to be viewed in the UI and present only the current row contents. A
>> separate
>> view would display a histo
On 01/03/2013 07:38 AM, Rich Shepard wrote:
The middleware of the application needs to check this table when data
are
to be viewed in the UI and present only the current row contents. A
separate
view would display a history of changes for that row.
All thoughts, suggestions, and recommen
14 matches
Mail list logo
