Message-ID: <f260c14e9e70e43cc956e99dc11ca6ce16d73c57.camel@cybertec.at>
Subject: Re: Regarding setClob and getclobval methods in PostgreSQL
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Rajyalakshmi Sareddy <rajyalakshmi.x.sareddy@gsk.com>,
 "pgsql-novice@postgresql.org"
	 <pgsql-novice@postgresql.org>
Date: Sat, 01 Feb 2025 00:42:50 +0100
In-Reply-To: 
 <AM6P137MB01308BAB4D2504725635DBBBD6E82@AM6P137MB0130.EURP137.PROD.OUTLOOK.COM>
References: 
	<AM6P137MB01308BAB4D2504725635DBBBD6E82@AM6P137MB0130.EURP137.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/f260c14e9e70e43cc956e99dc11ca6ce16d73c57.camel%40cybertec.at>
Precedence: bulk

On Fri, 2025-01-31 at 11:35 +0000, Rajyalakshmi Sareddy wrote:
> We are currently migrating the code from oracle to postgresql and using j=
dbc
> jar ispostgresql-42.7.4.jar. But for code migration, we are getting error=
s
> like org.postgresql.jdbc.PgPreparedStatement.setClob(int, Reader) is not =
yet
> implemented.
> =C2=A0
> Could you please confirm on setClob and getclobval methods are implemente=
d
> in postgresql-42.7.4 jar. =C2=A0If not implemented, could you please sugg=
est
> with alternate methods.

I can only confirm that that method is *not* implemented.
You would have to use setClob(int parameterIndex, Clob x) instead.

But really, *do not* use any of the getClob and setClob methods, because th=
ey
use Large Objects in PostgreSQL, and you should avoid Large Objects.

Use setBinaryStream(int parameterIndex, InputStream x) instead, so that
you can use "bytea" in the database.

By the way, there is a specific mailing list for the JDBC driver, where you
may get better answers.

Yours,
Laurenz Albe