From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Adding \ev view editor? |
Date: | 2009-09-02 12:07:13 |
Message-ID: | b42b73150909020507s4b4fd56au1330658112476d67@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 1, 2009 at 2:41 PM, Josh Berkus<josh(at)agliodbs(dot)com> wrote:
> All,
>
> I've grown to adore the new \ef function editor.
>
> It doesn't seem like it would be that difficult to add a view editor as
> \ev. While editors would also be good for other objects, I don't think
> we can do \et or \er etc. because those objects don't support CREATE OR
> REPLACE.
>
> Opinions? Other objects which could take \e?
One reason I don't like this proposal is that postgresql does not
preserve the original 'create view' statement for editing. The
resulting sql that is given to you to edit is hopelessly mangled and I
think it's not good to encourage people to modify views in this
fashion.
Then again, we are only reproducing what pgadmin can already do, so why not? :-)
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Nacos | 2009-09-02 12:21:05 | trigger SPI_exec count argument |
Previous Message | Pavel Stehule | 2009-09-02 12:02:46 | window functions maybe bug |