-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> 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.
I agree, just wanted to see how pedantic we were going to be. As long
as nobody is using the output of psql for input into a script, we
should be fine.
> 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...)
Agreed: I'll remove that odd quoting in my next patch if nobody else obejcts.
> For that matter, wouldn't consistency require that column headings
> in SELECT results be quoted similarly?
Yes, that would be consistently ugly. :)
> 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.
I don't agree with this. We already discriminate against system objects by
not showing system tables, for example, when doing a \dt. There is no reason
I should have to scroll through 1500+ system functions using \df because I
forgot the name of one of the 12 functions I've created, or simply because
I want to view all 12 quickly.
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200408291827
-----BEGIN PGP SIGNATURE-----
iD8DBQFBMlj2vJuQZxSWSsgRAtOIAJ4mpzC/pSzDcVSjRSecwoGVYUOScgCg150m
m4qpZuc7wT0998bNyPQWU6E=
=yXLQ
-----END PGP SIGNATURE-----
