From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org, SAKAIDA <sakaida(at)psn(dot)co(dot)jp> |
Subject: | Re: psql \l error |
Date: | 2000-05-02 10:15:37 |
Message-ID: | 390EAAC9.436770A4@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> On Tue, 2 May 2000, Hiroshi Inoue wrote:
>
> > What kind of backward compatibity is required for psql etc..?
>
> I thought psql was some sort of a reference application, so sticking to
> prehistoric technology is not necessarily required. For example, outer
> joins will simplify psql a great deal but that would really mean it stops
> working for everybody else. Not sure.
>
> The knowledge about the system catalogs is already pretty deep so keeping
> track of changes across versions is similar to the initdb problem:
Yes there's another example. PostgreSQL odbc driver wasn't able to talk
to 7.0 backend until recently due to the change int28 -> int2vector.
Now odbc driver could talk to all the backends from 6.2.
We may have to hold some reference table between system catalogs
and client appl/lib.
>
> > Are there any documentations about it ?
>
> Yes.
Unfortunately it's always painful for me to look for a documentation.
Could you please tell me where we could find it ?
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-02 10:54:01 | Re: Update to FAQ_SCO. |
Previous Message | SAKAIDA | 2000-05-02 09:17:13 | Re: psql \l error |