Dennis Björklund wrote:
> > What is wrong with
> >
> > SELECT * FROM information_schema.tables;
>
> The result is very hard to read since it's so much of it (try column
> instead of tables). The \xx commands do some nice formatting you
> don't get from the above.
This is an interesting point to re
Tom Lane wrote:
> 2. Some people aren't using psql.
I don't see why this is an issue. People not using psql are either
using a GUI, which presumably supports plenty of "show" and "describe"
functionality, or they're writing their own program, in which case it
doesn't really matter how sh
On Sat, 10 Jan 2004, Tom Lane wrote:
> ISTM there are three fundamental problems with \d and friends:
>
> 1. Some people have a hard time remembering the commands.
> 2. Some people aren't using psql.
> 3. psql keeps breaking across backend versions because the
> needed
Merlin Moncure kirjutas R, 09.01.2004 kell 22:04:
> Peter Eisentraut wrote:
> > The central problem I have is this: How do we deal with the fact that
> > an XML datum carries its own encoding information?
>
> Maybe I am misunderstanding your question, but IMO postgres should be
> treating xml doc
Greg Stark <[EMAIL PROTECTED]> writes:
> So for example:
> \describe table foo => \dt foo
> \describe index foo => \di foo
> \describe aggregate foo => \da foo
> \describe operator foo => \do foo
It doesn't seem to me that this buys much except verboseness, though.
ISTM there are three fundament
Andreas Pflug wrote:
Sounds good. While I probably won't find time helping implementing the
driver; I have an OLEDB app running that currently uses
MSDASQL/psqlODBC. I'd certainly like testing your driver, and give
feedback from that.
That would be great.
When do you expect first usable versio
Dennis Björklund <[EMAIL PROTECTED]> writes:
> I would rather have long commands so one can write
>
> \describe_table foo
I would think it would be better to keep everything under a single command and
have a 1-1 correspondence to \d. Ie, just add a long form syntax following the
existing \d. \d
Shachar Shemesh wrote:
Andreas Pflug wrote:
I wonder if this could be implemented as a wrapper around libpq. This
way, the OLEDB driver would benefit from a proven piece of software.
Regards,
Andreas
That's what I'm doing. I'm not sure why other drivers didn't do that
as well (maybe there wa
On Sat, 10 Jan 2004, Peter Eisentraut wrote:
> > to remember way of showing the various entities in psql (at the very
> > least) would be of great advantage. It's something that MySQL gets
> > right. As it turns out, we already have "SHOW" in psql and it's used
> > for something else.
>
> What
Kevin Brown wrote:
> Every database engine is different, but in the case of PG it makes
> sense to adopt the best methods we can find. A consistent and easy
> to remember way of showing the various entities in psql (at the very
> least) would be of great advantage. It's something that MySQL gets
Alex J. Avriette wrote:
> On Sun, Jan 04, 2004 at 07:59:02PM -0600, D. Dante Lorenso wrote:
>
> > Anything other than simple, short commands is a waste, IMHO. I can easily
> > remember SHOW DATABASES and SHOW TABLES and DESC , because they
> > reflect
> > my intensions directly and 'make sense'.
11 matches
Mail list logo
