-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> One issue here is that plain \d gets less useful because it'll now
> include system catalogs.
Are you kidding me? No way. That's a recipe for making all our users
unhappy with us.
> * \dfU will restrict the printout to non-system functions
Sorry, but the "U" is ugly and unnecessary. The *default* should always
be user-defined functions, and to hide the internals. Hence, we have a
special flag for when you know what you are doing and want to see the system
information: "S".
I do agree that \d is not consistent with anything else, but let's not
throw the baby out with the bathwater. Or if we do, let's not have \d
show sequences either, because that part always annoyed me. :)
> Comments? Does this cover all the cases?
No: the user case someone had upthread, where they want to see all their
functions starting with an "a" across all schemas in their path:
\df a*
This should act similar to how \dt does right now:
\dt p*
Such that it shows only the user's functions, and only the user's tables.
99% of the time, people don't care about or want to see the 60+ internal
functions starting with "a", and the 40 or so internal tables
starting with "p".
I'm willing to concede some of the "\d.{1} objectname" behavior, but I don't
think we should mess at all with "\d" or "\dt" because people are used
to the current behavior, and its rather sane and useful (unlike \df)
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200901161234
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAklwxXgACgkQvJuQZxSWSsgawACeMox6/RveSyvRJ4gpe/TiLSR3
YeYAoOBxy6IpTLdHYI40haMAgCebobLB
=Dj3a
-----END PGP SIGNATURE-----