| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: \d+ for long view definitions? |
| Date: | 2009-09-01 19:01:10 |
| Message-ID: | 20090901190109.GV20482@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 01, 2009 at 02:29:12PM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > I think we should always or never show the view definition, not
> > sometimes.
>
> Yeah. I can live with \d not showing it and \d+ showing it --- as
> Peter already mentioned, that would be consistent with \df behavior.
> Making it depend on the length is just weird.
As I see it, there are two independent issues here:
* "Smart" display based on number of columns in the query and the psql window
* Whether to display the view definition.
I'm thinking on the second, \d should not display the definition, and
\d+ should.
On the first...could we go to \x-type display if the columns will
overflow the terminal?
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2009-09-01 19:03:43 | Re: Adding \ev view editor? |
| Previous Message | Josh Berkus | 2009-09-01 18:41:31 | Adding \ev view editor? |