| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Rod Taylor <rbt(at)rbt(dot)ca> |
| 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 01:24:51 |
| Message-ID: | 3F95DC63.3090905@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
We could use information_schema...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-10-22 01:25:34 | Re: multi-backend psql |
| Previous Message | Justin Clift | 2003-10-22 00:41:57 | Re: [HACKERS] Mapping Oracle types to PostgreSQL |