| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch: Add columns via CREATE OR REPLACE VIEW |
| Date: | 2008-08-07 18:34:32 |
| Message-ID: | 603c8f070808071134o39919af2q29df2ca66d405dfa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> I was thinking that the ADD COLUMN should specify the new result list
>> entry.
>
> Yeah, that's what I was thinking too. If you needed to change more
> than just the topmost SELECT list, you'd need two steps: an ADD COLUMN
> and then CREATE OR REPLACE VIEW to change the query in some way that
> doesn't result in changing the output column set. Maybe that's going
> to be too awkward to use though.
To me, that sounds less useful than simply being able to make changes
via CREATE OR REPLACE VIEW, but it's not an either/or proposition, and
I suspect that it's significantly more complicated to implement than
the patch I submitted.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-08-07 19:03:49 | Re: patch: Add columns via CREATE OR REPLACE VIEW |
| Previous Message | Tom Lane | 2008-08-07 18:13:17 | Re: patch: Add columns via CREATE OR REPLACE VIEW |