Re: Database Design: Maintain Audit Trail of Changes

Поиск
Список
Период
Сортировка
От Rich Shepard
Тема Re: Database Design: Maintain Audit Trail of Changes
Дата
Msg-id alpine.LNX.2.00.1301030848120.5088@salmo.appl-ecosys.com
обсуждение исходный текст
Ответ на Re: Database Design: Maintain Audit Trail of Changes  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Ответы Re: Database Design: Maintain Audit Trail of Changes  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Список pgsql-general
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
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 prevent data manipulation such as was done several years ago by
the president of Southwestern Resources (a gold mining company) to pump up
the company's stock price by changing assay results.

Rich



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

Предыдущее
От: Fabrízio de Royes Mello
Дата:
Сообщение: Re: Database Design: Maintain Audit Trail of Changes
Следующее
От: Rich Shepard
Дата:
Сообщение: Re: Database Design: Maintain Audit Trail of Changes