Kevin,
* Kevin Grittner (Kevin.Grittner@wicourts.gov) wrote:
> I can't picture anything which could be done with views which would
> allow me to issue one statement and see everything of interest about
> a table (etc.). You know: tablespace, owner, permissions, columns,
> primary key, foreign keys, check constraints, exclusion constraints,
> ancestor tables, child tables, and whatever interesting features I
> missed or we later add.
You think that the users of the libpq() interface (or even the protocol
itself) are going to handle getting \dt-type output back somehow..? As
what, a single-column result of type text? And then they'll use
non-fixed-width fonts, undoubtably, which means the results will end up
looking rather ugly, even if we put in the effort to format the results.
I'm becoming more and more inclined to just address this with
newsysviews and encouraging use of the existing TABLE top-level command
for people who have issue with 'SELECT *'.
> Other products allow that to be generated
> server-side, so that it is available to any and all clients. I
> think we should join the crowd in this respect.
I could see some things being done this way, but the entire \dt output
for a given table strikes me as stretching it pretty far.. And only
doing it half-way doesn't strike me as a very good idea.
Thanks,
Stephen