| From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
|---|---|
| To: | Tony Theodore <tonyt(at)logyst(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Database Design: Maintain Audit Trail of Changes |
| Date: | 2014-04-13 15:09:23 |
| Message-ID: | CAJ4CxLk4p8rzXnK0RxOEEkXOOmJ5s52no+Et4T9Vp0uqZoM5uw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Apr 12, 2014 at 2:57 AM, Tony Theodore <tonyt(at)logyst(dot)com> 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.
>>
>
> Do you plan to support primary keys other than single column integers?
>
I may modify it to support bigints, but I don't have any plans to support
multi-column primary keys. It would require too much overhaul of the code.
Moshe Jacobson
Manager of Systems Engineering, Nead Werx Inc. <http://www.neadwerx.com>
2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339
"Quality is not an act, it is a habit." -- Aristotle
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Jones | 2014-04-13 20:29:11 | User defined operator fails to work in EXCLUDE constraint |
| Previous Message | Torsten Förtsch | 2014-04-13 13:23:51 | Re: Why do we need an AccessExclusiveLock to validate a FK constraint marked as NOT VALID? |