Re: [HACKERS] psql: \x and slash commands

2005-06-13 Thread Robert Treat
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

Re: [HACKERS] psql: \x and slash commands

2005-06-12 Thread Jon Jensen
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

[HACKERS] psql: \x and slash commands

2005-06-09 Thread Neil Conway
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

Re: [HACKERS] psql: \x and slash commands

2005-06-09 Thread Christopher Kings-Lynne
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