When you turn on \x mode for query output in psql, it wrecks the output
of \d , etc.
Should we change it so that the \d is unaffected by \x? What about for
other \d commands?
Well, they asked for \x so why is it wrong for us to \x the \d output
like we do now?
Because I have the feeling (back m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
> "Wrecks" to you maybe ... but if someone likes \x display, why wouldn't
> they like it for \d too?
>
> One could argue that the real bug is that the footers in \d don't change
> to look like \x output.
Indeed, it behaves exactly th
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> When you turn on \x mode for query output in psql, it wrecks the output
> of \d , etc.
"Wrecks" to you maybe ... but if someone likes \x display, why wouldn't
they like it for \d too?
One could argue that the real bug is that the footers in \
Christopher Kings-Lynne wrote:
> When you turn on \x mode for query output in psql, it wrecks the output
> of \d , etc.
>
> Should we change it so that the \d is unaffected by \x? What about for
> other \d commands?
Well, they asked for \x so why is it wrong for us to \x the \d output
like we
When you turn on \x mode for query output in psql, it wrecks the output
of \d , etc.
Should we change it so that the \d is unaffected by \x? What about for
other \d commands?
Chris
---(end of broadcast)---
TIP 3: if posting/reading through Usenet
