Re: fake vs real CREATE OR REPLACE VIEW

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: fake vs real CREATE OR REPLACE VIEW
Date: 2002-02-26 10:19:20
Message-ID: FED2B709E3270E4B903EB0175A49BCB1047615@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 26 February 2002 09:28
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] fake vs real CREATE OR REPLACE VIEW
>
>
> Le Mardi 26 Février 2002 09:40, Dave Page a écrit :
> > Yes. I thought I suggested adding a warning to that effect at one
> > time.
> You are right. We could query using existing views with ILIKE
> %view_bar% and
> issue a warning if some view matches, but this wron't fix the
> broblem. We
> need CREATE OR REPLACE VIEW... CREATE OR REPLACE TRIGGER is
> not really
> needed...
>
> > How's the ALTER VIEW patch coming along btw?
> Do you mean issuing a warning?

No, you were looking at a list of issues I had. I haven't had a chance to
check the code yet - you may have already committed it.

/D

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2002-02-26 10:30:25 Re: Database->ServerEncoding, ClientEncoding
Previous Message Jean-Michel POURE 2002-02-26 09:43:30 Re: Database->ServerEncoding, ClientEncoding