Re: cyclical redundancy checksum algorithm(s)?

Поиск
Список
Период
Сортировка
От Joachim Wieland
Тема Re: cyclical redundancy checksum algorithm(s)?
Дата
Msg-id 20060928083015.GA2663@mcknight.de
обсуждение исходный текст
Ответ на Re: cyclical redundancy checksum algorithm(s)?  (John Sidney-Woollett <johnsw@wardbrook.com>)
Ответы Re: cyclical redundancy checksum algorithm(s)?
Re: cyclical redundancy checksum algorithm(s)?
Список pgsql-general
On Thu, Sep 28, 2006 at 07:09:43AM +0100, John Sidney-Woollett wrote:
> Why not use an update trigger on the affected tables to record a
> lastupdated timestamp value when the record is changed.

> Surely this is simpler thanks computing some kind of row hash?

It depends on how you define "change". With the triggers you propose an

UPDATE table SET col = col;

is a change because there was a write operation. Any hash function's output
would be "no change" because the actual data did not change. An update might
entail an expensive update of some external data so you might want to make
sure that data really got modified.

--
Joachim Wieland                                              joe@mcknight.de
                                                           GPG key available

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

Предыдущее
От: "A. Kretschmer"
Дата:
Сообщение: Re: Definition of return types for own functions?
Следующее
От: John Sidney-Woollett
Дата:
Сообщение: Re: cyclical redundancy checksum algorithm(s)?