| From: | "Chris Velevitch" <chris(dot)velevitch(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: What is the point of create or replace view command |
| Date: | 2006-06-05 04:23:35 |
| Message-ID: | b0a3bf780606042123l55afa30dtcf69e133f2977ef0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/5/06, Berend Tober wrote:
> Chris Velevitch wrote:
> > What is the point of the create or replace view command if you can't
> > change the column and data types ?
>
> You could have a calculated column and change the calcuation.
>
> You could change the sort order, selection, or grouping clauses.
That's what I'm trying to do but the command won't let me. So what's
the point of having such a if it won't replace the previous
definition. I ended up having to drop and the create it again. I'm
trying to understand the reasoning behind the limit in functionality
of the command. With my current understanding, it's very useful and
should be dropped from postgres.
Chris
--
Chris Velevitch
Manager - Sydney Flash Platform Developers Group
www.flashdev.org.au
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Velevitch | 2006-06-05 04:25:47 | Re: What is the point of create or replace view command |
| Previous Message | Lincoln Yeoh | 2006-06-05 03:39:44 | Re: PGSQL 7.4 -> 8.1 migration & performance problem |