From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Barry Lind <barry(at)xythos(dot)com> |
Cc: | Bruce Toback <btoback(at)mac(dot)com>, Barry Lind <blind(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Re: [HACKERS] JDBC adaptor issue |
Date: | 2001-07-11 17:43:54 |
Message-ID: | 200107111743.f6BHhs817911@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
> Actually the problem is worse than I thought. Not only do all the
> get/setXXXStream methods assume the datatype is a BLOB, but also the
> get/setBytes methods. This means that it isn't possible to support
> bytea as the binary datatype without also breaking some backward
> compatability.
>
> In looking at the CVS log, it appears that the stream methods were only
> introduced in the 7.1 JDBC driver, since 7.1 has only been out
> (production) a few months, the number of people affected will be
> smaller, the setBytes() method that assumed a blob was there in 7.0, so
> it is likely more people will be impacted by any change there.
If you are looking for votes, you can break backward compatibility here.
--
Bruce Momjian | http://candle.pha.pa.us
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 | Peter Eisentraut | 2001-07-11 17:46:08 | Re: Re: SOMAXCONN (was Re: Solaris source code) |
Previous Message | Bruce Momjian | 2001-07-11 17:35:56 | Re: Re: Multiple Indexing, performance impact |
From | Date | Subject | |
---|---|---|---|
Next Message | Dejan Vucinic | 2001-07-11 17:45:25 | can't write a BLOB, 7.1.2 |
Previous Message | Dejan Vucinic | 2001-07-11 17:42:42 | [PATCH] setTimestamp(int, Timestamp) fails on null timestamp |