Re: Regarding setClob and getclobval methods in PostgreSQL - Mailing list pgsql-novice

From Laurenz Albe
Subject Re: Regarding setClob and getclobval methods in PostgreSQL
Date
Msg-id f260c14e9e70e43cc956e99dc11ca6ce16d73c57.camel@cybertec.at
Whole thread Raw
List pgsql-novice
On Fri, 2025-01-31 at 11:35 +0000, Rajyalakshmi Sareddy wrote:
> We are currently migrating the code from oracle to postgresql and using jdbc
> jar ispostgresql-42.7.4.jar. But for code migration, we are getting errors
> like org.postgresql.jdbc.PgPreparedStatement.setClob(int, Reader) is not yet
> implemented.
>  
> Could you please confirm on setClob and getclobval methods are implemented
> in postgresql-42.7.4 jar.  If not implemented, could you please suggest
> 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 they
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



pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: btree_gin, bigint and number literals
Next
From: Rajyalakshmi Sareddy
Date:
Subject: RE: Regarding setClob and getclobval methods in PostgreSQL