Re: Affected # of Rows After TRIGGER/RULE Return

From: Volkan YAZICI <yazicivo(at)ttmail(dot)com>
To: bopolissimus(at)gmail(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Affected # of Rows After TRIGGER/RULE Return
Date: 2008-05-14 08:33:56
Message-ID: 87iqxhi8sr.fsf@alamut.mobiliz.com.tr
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 14 May 2008, Gerald Quimpo <bopolissimus(dot)lists(at)gmail(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message J. Manuel Velasco - UBILIBET 2008-05-14 08:35:01 Re: how can i get initdb
Previous Message J. Manuel Velasco - UBILIBET 2008-05-14 08:33:41 Re: change encoding