From: Neil Conway <neilc@samurai.com>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: Hannu Krosing <hannu@tm.ee>
Cc: greg@turnstep.com, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Are we losing momentum?
Date: 21 Apr 2003 13:06:01 -0400
Message-ID: <1050944761.1062.7.camel@tokyo> (raw)
In-Reply-To: <Pine.LNX.4.33.0304210927550.5883-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0304210927550.5883-100000@css120.ihs.com>
On Mon, 2003-04-21 at 11:30, scott.marlowe wrote:
> 'show tables' is SQL, and can be run from a script, with the output
> parsed.
But "select * from pg_tables" (or the equivalent query on the
information schemas) is SQL, can be run from a script, and can be parsed
by a client application.
> But, how do I write an app to ask such questions easily? psql -E is not
> the easiest and most intuitive way to learn how to get the data into a
> structure for parsing in a client side app.
You're conflating two distinct issues: (1) providing an interface for
CLI use by the DBA (2) providing an API for programmer use in
applications.
If you think the existing system catalogs are not sufficiently
intuitive, then we should fix that problem properly (for example,
through better documentation), not by copying some ad-hoc syntax from
another RDBMS.
If you think the existing CLI interface (\d etc.) is not sufficiently
intuitive (which has been what a couple people in this thread have
argued), I don't see what that has to do with client side applications
or parsing the output.
Cheers,
Neil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: neilc@samurai.com, scott.marlowe@ihs.com, hannu@tm.ee
Subject: Re: Are we losing momentum?
In-Reply-To: <1050944761.1062.7.camel@tokyo>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox