Re: Should PG backend know how to represent metadata?

At 16:30 17/07/00 +1000, Chris Bitmead wrote:
>
>Something like...
># \D table foo
>
>create table foo (
> bar text,
> baz integer
>);

Exactly. Also, "\D table" would list all tables.

The idea is to have [a replacement for] the 'dump' code from pg_dump in the
backend or in a library (libpq? libdump?). It might also be worth allowing:

\D ALL

to do something close to what pg_dump does at the moment (ie. raw text dump
of schema), although I would probably be inclined to sort the output in
logical order (all tables together etc).

As has already been commented, the changes I have made to pg_dump are
non-trivial, so now might be a good time to make these extra changes.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/