From: | snpe <snpe(at)snpe(dot)co(dot)yu> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: create or replace view |
Date: | 2002-11-14 16:17:15 |
Message-ID: | 200211141617.15247.snpe@snpe.co.yu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thursday 14 November 2002 02:41 pm, Bruno Wolff III wrote:
> On Thu, Nov 14, 2002 at 13:41:18 +0000,
>
> snpe <snpe(at)snpe(dot)co(dot)yu> wrote:
> > Hello,
> > When I change view and change number of column PostgreSQL return error
> > : 'cannot change number of column in view'
> > Is it too hard set this command
> > if view exits drop view
> > and then change view
> >
> > It is like with return type in function
> >
> > Now 'or replace' don't help too much
>
> The create or replace command exists so that you can modify a view in a
> way that allows other objects that refer to it to keep working (without
> having to recreate those objects). However if you can the number of
> columns (and probably any of their types), then these other objects
> or going to need to know that things have changed so that you can't
> just replace the view.
I undestand that, but if I change number of column I want that
'create or replace view' do 'drop view ..; create view ..;'
Why not ?
regards
Haris Peco
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 2002-11-14 16:20:20 | Re: Propose RC1 for Friday ... |
Previous Message | Bruce Momjian | 2002-11-14 16:03:53 | Re: Does v7.2.x support AIX 5.1? |