BUG #1205: psql toggles

From: "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1205: psql toggles
Date: 2004-08-05 14:27:32
Message-ID: 20040805142732.2574CCF4BCD@www.postgresql.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 1205
Logged by: Doug Bloebaum

Email address: bloebaum(at)dma(dot)org

PostgreSQL version: 7.4

Operating system: SuSE Linux 9.1 (i586)

Description: psql toggles

Details:

This is a feature request, not a bug:

In psql there is an internal slash command \t (and the equivalent \pset
tuples_only) which toggles a "rows only" result mode.

The problem is that when writing utility SQL scripts to create output, you
can't tell which mode you're toggling to, as the user may have changed
settings within the current session. The same can be said for all the
"toggle" commands, really.

My request is that at least the \pset versions of the toggle commands take
an "on" or "off" argument, in order to make setting things more discrete.
Something like:

\pset tuples_only off
\pset tuples_only on

Thanks for listening!

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-08-05 19:04:10 BUG #1206: sig fault 12 and core dumps using conflux
Previous Message Joe Conway 2004-08-05 06:01:06 Re: [BUGS] casting strings to multidimensional arrays yields strange