Re: psql questions: SQL, progname, copyright dates - Mailing list pgsql-hackers

From Tom Lane
Subject Re: psql questions: SQL, progname, copyright dates
Date
Msg-id 18152.1093789645@sss.pgh.pa.us
Whole thread Raw
In response to Re: psql questions: SQL, progname, copyright dates  ("Greg Sabino Mullane" <greg@turnstep.com>)
Responses Re: psql questions: SQL, progname, copyright dates  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-hackers
"Greg Sabino Mullane" <greg@turnstep.com> writes:
> This should be:
> Table "public.Upper Division"
>       Column      |  Type   | Modifiers
> ------------------+---------+-----------
>  abc              | integer |
>  " spaced out  "  | text    |
>  " real ""Name""" | text    |
>  "MixedCase"      | text    |

I find this quite ugly, and don't think it's a good change.  Anyone
who's fool enough to use trailing spaces in column names deserves the
pain it will cost them --- and there is no other case in which the
unquoted display is ambiguous.

If we are going to go over to a policy of displaying names the same way
you'd have to type them, what of the table name at the top of the
output?  (I actually would vote for some change there, because I think
the way we are quoting the whole thing is actively misleading...)
For that matter, wouldn't consistency require that column headings
in SELECT results be quoted similarly?

On the ordering issues, I'd go for straight alphabetical schema/name
sort in all cases; I thought that's where we were already, but if you
see some missing cases let's fix it.  I'm not enamored of discriminating
against system objects in the sort order.
        regards, tom lane


pgsql-hackers by date:

Previous
From: pgsql@mohawksoft.com
Date:
Subject: Re: Contrib -- PostgreSQL shared variables
Next
From: Greg Stark
Date:
Subject: Re: Contrib -- PostgreSQL shared variables