Re: Affected # of Rows After TRIGGER/RULE Return

Поиск
Список
Период
Сортировка
От Volkan YAZICI
Тема Re: Affected # of Rows After TRIGGER/RULE Return
Дата
Msg-id 87iqxhi8sr.fsf@alamut.mobiliz.com.tr
обсуждение исходный текст
Ответ на Re: Affected # of Rows After TRIGGER/RULE Return  (Gerald Quimpo <bopolissimus.lists@gmail.com>)
Список pgsql-general
On Wed, 14 May 2008, Gerald Quimpo <bopolissimus.lists@gmail.com> writes:
> Not really :-).  I was just looking at the simplest possible thing that could
> work.  I've looked at versioned/temporal databases.  But you probably
> can't go there since it definitely adds a lot of complexity to your app
> and queries.  Are you able to change your representation of "deleted"
> rows?  e.g., can you have an
>
>      is_deleted boolean not null default false
>
> column there?  that's how i'd have gone, myself, instead of mangling
> the plate number.

That's really how it should be done. But there are really significant
design mistakes made years ago, and I gave up messing with them. Will
just accomplish migration and that's all.


Regards.

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

Предыдущее
От: "J. Manuel Velasco - UBILIBET"
Дата:
Сообщение: Re: change encoding
Следующее
От: "J. Manuel Velasco - UBILIBET"
Дата:
Сообщение: Re: how can i get initdb