From: | Sven Köhler <skoehler(at)upb(dot)de> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: BLOBs etc |
Date: | 2005-01-07 03:04:38 |
Message-ID: | 41DDFC46.1080807@upb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
>>on the jdbc-webpages it says, that the JDBC team may decide to change
>>getBLOBG/setBLOB to support bytea only, and that one should use the
>>PostGreSQL specific LargeObject extension to acces them.
>
> I'm not sure where it says that, but it is either out of date or just
> plain bad advice. If you could point out where it says that I'd
> appreciate it. I would stick withe the standard Blob interface for now.
http://www.postgresql.org/docs/7.4/static/jdbc-binary-data.html
There is says:
Note: In a future release of the JDBC driver, the getBLOB() and
setBLOB() methods may no longer interact with Large Objects and will
instead work on the data type bytea. So it is recommended that you use
the LargeObject API if you intend to use Large Objects.
BTW: why don't getInputStream/getBLOB/... work for _both_, bytea and
oid? Shouldn't the JDBC driver be abled to determine the used datatype
and act accordingly? I'm sure you had you reasons. I'd just like to know
them.
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2005-01-07 03:19:09 | Re: BLOBs etc |
Previous Message | Kris Jurka | 2005-01-07 02:44:12 | Re: BLOBs etc |