Re: Database Design: Maintain Audit Trail of Changes

Поиск
Список
Период
Сортировка
От Wolfgang Keller
Тема Re: Database Design: Maintain Audit Trail of Changes
Дата
Msg-id 20130108162007.89b280fef253133e9a605947@gmx.net
обсуждение исходный текст
Ответ на Database Design: Maintain Audit Trail of Changes  (Rich Shepard <rshepard@appl-ecosys.com>)
Список pgsql-general
>    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 who
modifies the data may be required to enter manually, couldn't the
function of simply tracking what was inserted, updated and deleted be
implemented by an "eternal" transaction log that never gets purged, but
regularly archived in partitions, PGP-signed (with a qualified key) if
required to prove authenticity?

After all, PostgreSQL maintains this automatically anyway, so why not
use it?

TIA,

Sincerely,

Wolfgang


В списке pgsql-general по дате отправления:

Предыдущее
От: Graeme Hinchliffe
Дата:
Сообщение: Using composite types within PLPGSQL Function
Следующее
От: Stefan Keller
Дата:
Сообщение: Query with LIMIT but as random result set?