Lists: | pgsql-hackers |
---|
From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | psql: \x and slash commands |
Date: | 2005-06-10 01:53:22 |
Message-ID: | 42A8F292.8060206@samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Someone commented to me recently that they usually use psql's \x
"expanded output" mode, but find that it produces pretty illegible
results for psql slash commands such as \d. I can't really see a reason
you would _want_ "expanded output" mode for the result sets of psql
slash commands. Would anyone object to changing \x to not affect that
way that the result sets of slash commands are printed?
-Neil
From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: \x and slash commands |
Date: | 2005-06-10 02:03:44 |
Message-ID: | 42A8F500.4030503@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
> Someone commented to me recently that they usually use psql's \x
> "expanded output" mode, but find that it produces pretty illegible
> results for psql slash commands such as \d. I can't really see a reason
> you would _want_ "expanded output" mode for the result sets of psql
> slash commands. Would anyone object to changing \x to not affect that
> way that the result sets of slash commands are printed?
I have complained about that a few times before, but for some
unbeknownst reason people thought that having totally messed up table
displays was a feature, not a bug :)
Chris
From: | Jon Jensen <jon(at)endpoint(dot)com> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: \x and slash commands |
Date: | 2005-06-10 16:42:57 |
Message-ID: | Pine.LNX.4.63.0506101041370.11665@ynfu.ovalna.fjrygre.arg |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Fri, 10 Jun 2005, Neil Conway wrote:
> Someone commented to me recently that they usually use psql's \x "expanded
> output" mode, but find that it produces pretty illegible results for psql
> slash commands such as \d. I can't really see a reason you would _want_
> "expanded output" mode for the result sets of psql slash commands. Would
> anyone object to changing \x to not affect that way that the result sets of
> slash commands are printed?
I would very much like to see that behavior changed, but if there are
people who like it the way it is, maybe we can have a \X command that uses
expanded mode only for non-slash output.
What do others think about this?
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: \x and slash commands |
Date: | 2005-06-13 17:48:04 |
Message-ID: | 200506131348.04665.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Thursday 09 June 2005 22:03, Christopher Kings-Lynne wrote:
> > Someone commented to me recently that they usually use psql's \x
> > "expanded output" mode, but find that it produces pretty illegible
> > results for psql slash commands such as \d. I can't really see a reason
> > you would _want_ "expanded output" mode for the result sets of psql
> > slash commands. Would anyone object to changing \x to not affect that
> > way that the result sets of slash commands are printed?
>
> I have complained about that a few times before, but for some
> unbeknownst reason people thought that having totally messed up table
> displays was a feature, not a bug :)
>
If have found that \x on and \df+ can often produce nice results (especially
with a lot of \n in the function definitions.) I'm more neutral toward other
other things (\d on a table is kind of ugly, but \dv isnt so bad), but
wouldn't want to have to choose which ones some people would like and which
ones they wouldn't
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL