Re: SHOW TABLES

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: <jd(at)commandprompt(dot)com>,"David Fetter" <david(at)fetter(dot)org>, "Guillaume Lelarge" <guillaume(at)lelarge(dot)info>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Bernd Helmle" <mailings(at)oopsware(dot)de>, <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: SHOW TABLES
Date: 2010-07-16 17:31:19
Message-ID: 4C4051170200002500033742@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Marc G. Fournier" <scrappy(at)hub(dot)org> wrote:

> Haven't experienced Sybase for 2 years in my last job, I can tell
> you that the sp_* commands are definitely non-intuitive :(

In general, I'd agree; although I think I got used to them about as
fast as the PostgreSQL backslash commands. In the particular case
of sp_help I would disagree; once you've heard that, it's pretty
easy to remember and it works for tables, views, stored procedures,
logs, rules, defaults, triggers, referential constraints, encryption
keys, and check constraints.

You type:

sp_help <pretty-much-any-database-object>

And you get information back which is both reasonably
human-digestable based on the formatting of result sets in whatever
client you're using, and reasonably machine-digestable based on
looking at the column headers of the result sets.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Maciek Sakrejda 2010-07-16 17:32:01 Re: Trouble with COPY IN
Previous Message Dimitri Fontaine 2010-07-16 17:26:27 Re: Synchronous replication