From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, 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 11:14:38 |
Message-ID: | 200005021114.HAA08878@candle.pha.pa.us |
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.
The big reason for the change is that int2vector is now more than 8
int2's (now 16), so there may be internal changes as well as a name
change for applications.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2000-05-02 11:15:46 | Re: [HACKERS] Request for 7.0 JDBC status |
Previous Message | Bruce Momjian | 2000-05-02 11:11:54 | Re: PgAccess 0.98.6 , a ugly bug fixed |