Re: FW: OID, compatible=7.1 and getBinaryStream() in

Поиск
Список
Период
Сортировка
Искать
От
Dave Cramer
Тема
Re: FW: OID, compatible=7.1 and getBinaryStream() in
Дата
Msg-id
1071676151.1686.593.camel@localhost.localdomain
Ответ на
Список
Дерево обсуждения
Re: FW: OID, compatible=7.1 and getBinaryStream() in 7.4driver "Alexey Yudichev" <Alexey@francoudi.com>
Re: FW: OID, compatible=7.1 and getBinaryStream() in Dave Cramer <pg@fastcrypt.com>
Re: FW: OID, compatible=7.1 and getBinaryStream() in Kris Jurka <books@ejurka.com>
Re: FW: OID, compatible=7.1 and getBinaryStream() in Oliver Jowett <oliver@opencloud.com>
Re: FW: OID, compatible=7.1 and getBinaryStream() in Barry Lind <blind@xythos.com>
Re: FW: OID, compatible=7.1 and getBinaryStream() in Kris Jurka <books@ejurka.com>
patched and backpatched,

thanks guys!

Dave
On Wed, 2003-12-17 at 10:03, Alexey Yudichev wrote:
>   I have applied the patch against my CVS sources, built a jar and tested it. Everything now seems to work fine. Once the patch is in CVS I will check it out and rebuild the driver to be used in our development environment.
> 
> -----Original Message-----
> From: Kris Jurka [mailto:books@ejurka.com]
> Sent: Wednesday, December 17, 2003 4:46 PM
> To: Alexey Yudichev
> Cc: pgsql-jdbc@postgresql.org
> Subject: Re: FW: [JDBC] OID, compatible=7.1 and getBinaryStream() in 7.4driver
> 
> 
> 
> 
> On Wed, 17 Dec 2003, Kris Jurka wrote:
> 
> >
> >
> > On Wed, 17 Dec 2003, Alexey Yudichev wrote:
> >
> > > [I can't use 7.1 style large objects with a 7.4 database.]
> >
> > Here's a patch to fix this.  The core problem was a check to determine
> > if it should use the version 2 or 3 protocol was checking the
> > server version instead of the compatibility version.  While
> > locating this I found two other bugs.  The query to retrieve the
> > oids for the large object functions had an incorrect WHERE clause
> > when trying to deal with schemas.  Also the V3 fastpath API didn't
> > handle multiargument functions properly.
> >
> 
> Actually the last part about multiargument functions was correct to begin
> with.  Here's the patch with only the first two changes.
> 
> Kris Jurka
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
> 
> 

В списке pgsql-jdbc по дате отправления
От: Tom Lane
Дата:
Сообщение: Re: unsubscribe
От: Kris Jurka
Дата:
FAQ