Re: multi-backend psql

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Rod Taylor <rbt(at)rbt(dot)ca>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: multi-backend psql
Date: 2003-10-23 10:23:22
Message-ID: 3F97AC1A.9080403@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rod Taylor wrote:

>On Tue, 2003-10-21 at 21:24, Christopher Kings-Lynne wrote:
>
>
>>>There is always the biggest evil of all... Putting SHOW / DESCRIBE /
>>>HELP commands into the backend itself. I'm sure the pgAdmin group likes
>>>that idea (they're probably tired of maintaining 4 different versions of
>>>queries for getting a list of tables). Any solution to make psql
>>>backward or forward compatible should go an additional step to assist
>>>other frontends as well.
>>>
>>>
>>All that means for phpPgAdmin and pgAdmin is that we'll have to support
>>5 different queries :P
>>
>>
>
>Yes, but I would hope it stops at 5, and over the next 3 years you don't
>have 10 different query forms.
>
>
>
>>We could use information_schema...
>>
>>
>
>Nay... I would expect a PostgreSQL specific information_schema to get
>just as much mucking around as the system tables, which means you are
>still maintaining a set of queries per release.
>
>
The problem about information_schema is that it's restricted to show
objects of the owner only. This is by spec, but will prevent us from
seeing all we need.
This might get better if we get rules.

Regards,
Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Haller 2003-10-23 11:01:16 Re: Automatic compat checking? (was 7.4 compatibility question)
Previous Message Richard Huxton 2003-10-23 10:06:55 Re: Automatic compat checking? (was 7.4 compatibility question)