Re: Database design: Backwards-compatible field addition

From: David <wizzardx(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Database design: Backwards-compatible field addition
Date: 2008-06-19 08:03:12
Message-ID: 18c1e6480806190103t63adc509p56e5e2268d4e4858@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>> Problem with this is that some RDBMS (Postgresql specifically) don't
>> let you run update statements on views.
>
> Given 1) the view will be "fairly uncomplicated" and hence
> "fairly straightforward" ON INSERT/UPDATE/DELETE rule can
> likely be added to it allowing for an apparently writable
> view.
>

Thanks for the info.

I had the mistaken idea that rules and triggers were only for real
tables & not views (I've never used them before).

I would like to avoid using them if possible (extra complexity, and
don't want to rename tables & make new views each time I need to make
backwards-incompatible app updates), but they are there if I need
them.

David.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Cyril SCETBON 2008-06-19 08:05:27 Re: Error when trying to drop a tablespace
Previous Message David 2008-06-19 07:39:38 Re: Database design: Storing app defaults