Search Postgresql Archives

Re: Affected # of Rows After TRIGGER/RULE Return

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 14 May 2008, Gerald Quimpo <bopolissimus.lists@xxxxxxxxx> 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.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux