| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: multi-backend psql |
| Date: | 2003-10-22 02:23:15 |
| Message-ID: | 1066789394.74834.4.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-22 02:49:47 | Re: [HACKERS] obj_description problems? |
| Previous Message | Christopher Kings-Lynne | 2003-10-22 02:21:30 | 7.4 compatibility question |