Search Postgresql Archives

Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: rmd22 <rohit.dhamane@xxxxxxxxx>
Subject: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
From: Matthew Walden <matthew.walden.list@xxxxxxxxx>
Date: Wed, 17 Nov 2010 15:04:11 +0000
Cc: pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <1290003966479-3269108.post@xxxxxxxxxxxxx>

You can create a trigger on the table to store the old/new values in an audit table if that is what you mean?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
  - From: rmd22
- Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
  - From: Andreas Kretschmer

References:
- Storing old and new tuple values after an UPDATE, INSERT or DELETE
  - From: rmd22

Prev by Date: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Next by Date: Re: interactive pager off
Previous by thread: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Next by thread: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux