| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ravi Katkar <Ravi(dot)Katkar(at)infor(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: drop view with out cascading the dependents |
| Date: | 2010-10-20 14:11:22 |
| Message-ID: | AANLkTiksOnpU3=GaWptT151KsojhCBfm2iukiOnru3s9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2010/10/19 Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>:
> On Tue, Oct 19, 2010 at 3:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Ravi Katkar <Ravi(dot)Katkar(at)infor(dot)com> writes:
>>> Is there any feature to drop the view with out cascading the dependents.
>>
>> No. But why don't you use CREATE OR REPLACE VIEW?
>>
> only caveat is, it won't work if he adds/removes any columns. CREATE
> OR REPLACE VIEW is rather useless in most practical implementations.
In recent versions of postgres (I think 8.4+?) you can add columns to
the view via create/replace (not drop of course). This greatly
reduces the practical annoyances of dropping view dependencies, at
least for me...
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viktor Bojović | 2010-10-20 14:27:15 | truncating or full vacuuming |
| Previous Message | Norberto Delle | 2010-10-20 13:54:00 | Trying to stop warm standby server service |