From: | "EBIHARA, Yuichiro" <ebihara(at)iplocks(dot)co(dot)jp> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: standard LOB support |
Date: | 2007-06-22 07:28:25 |
Message-ID: | 01b301c7b49e$f06fa6f0$4a0aa8c0@ipljp.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
Thomas,
> > According to JDBC 3.0 specifiction, those 4 methods may not be
> > compatible to BLOB/CLOB. Some databases may support them to
> access LOB
> > data but not all databases.
> >
> Hmm. At least for updating LOBs, "my method" should be
> "legal". This is a quote from jdbc-3_0-fr-spec.pdf
>
> "The setBinaryStream and setObject methods may also be used
> to set a Blob object as a parameter in a PreparedStatement
> object. The setAsciiStream, setCharacterStream, and setObject
> methods are alternate means of setting a Clob object as a parameter."
Sorry, my comment was partially incorrect.
See B-182(TABLE B-6) of the spec.
getBinaryStream()/getCharacterStream are not compatible to LOB.
Also, there were some limitations with Oracle JDBC "Thin" driver 9.2 and those methods didn't work
with LOB.
Thanks,
ebi
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2007-06-22 07:44:39 | Re: standard LOB support |
Previous Message | Thomas Kellerer | 2007-06-22 07:11:00 | Re: standard LOB support |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2007-06-22 07:44:39 | Re: standard LOB support |
Previous Message | Thomas Kellerer | 2007-06-22 07:11:00 | Re: standard LOB support |