>>Hi,
>>
>>I am considering using a PostgreSQL database as a backend for a system currently using DBFs. Can anyone recommend an Audit Trail that will allow me to track who made what changes to certain tables and when the changes were made? I am anticipating that my application will connect to the database using a single user, then will have its own user table which will contain the username/password hash to verify if the person has access to the system. It's this second user name that I will need to track as part of the audit trail.
>
>I'm just reviving this thread in the hopes that someone can recommend an Audit Trail that will work for PostgreSQL. I think the last discussion went off on a tangent (albeit a helpful one) and I still have no real solution. So, let's assume each user has their own login to the database, is there a tool out there which will generate the appropriate triggers and audit tables for me, or do I need to do it manually for each table I want to audit changes to?
Have you tried asking on a PG-specific forum?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up