Re: Adding \ev view editor?

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Adding \ev view editor?
Date: 2009-09-02 16:24:45
Message-ID: 343A4C4C-504E-4CB0-BAE7-C8EB0E4044D1@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sep 2, 2009, at 5:07 AM, Merlin Moncure wrote:

> 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? :-)

Is there any reason that the CREATE VIEW output to pg_dump and,
presumably, \ev, couldn't be refactored to pretty-print the VIEW
declaration?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-09-02 16:35:13 Re: Adding \ev view editor?
Previous Message Michael Nacos 2009-09-02 16:13:18 Re: trigger SPI_exec count argument