Re: psql \d option list overloaded

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "D(dot) Dante Lorenso" <dante(at)lorenso(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: psql \d option list overloaded
Date: 2004-01-04 07:22:10
Message-ID: 3FF7BF22.7040702@paradise.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

Couldn't agree more - syntax like

SHOW TABLES;

is inituitive and somehow "right" - [chuckles] - Mysql does not have
*everything* wrong!

regards

Mark

Bruce Momjian wrote:

>I like the idea of adding a new syntax to show that information using
>simple SQL command syntax, and putting it in the backend so all
>applications can access it. I know we have information schema, and
>maybe that can be used to make this simpler.
>
>
>

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Peter Eisentraut 2004-01-04 18:53:36 Re: psql \d option list overloaded
Previous Message Keith C. Perry 2004-01-04 01:58:11 Re: Is my MySQL Gaining ?

Browse pgsql-general by date

  From Date Subject
Next Message Mark Kirkwood 2004-01-04 07:27:39 Re: why the need for is null?
Previous Message Mark Kirkwood 2004-01-04 07:14:40 Re: TPC-C and Postgres

Browse pgsql-hackers by date

  From Date Subject
Next Message Martin Marques 2004-01-04 12:54:25 Re: time format
Previous Message Neil Conway 2004-01-04 06:56:27 Re: Lock contention (was Re: [PATCHES] update i386