Re: ResultSet.getClob() causing problems when used with JPA's @Lob

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Date: 2016-07-27 19:58:46
Message-ID: CAB=Je-FbszwjAFVYfr+DiGgS8dOhsOFTGK65=d7VyjPAHdnyvQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Thomas,

Thanks for looking into this, however could you please file a github PR so
the system tests the change against different PostgreSQL / Java versions?

Could you add a test case that explores ResultSet.getClob as well?

I think something similar is needed for PgPreparedStatement as well, but I
> did not find a way to check
> the type of a column the way it's done in PgResultSet. It seems that
> ParameterList.getTypeOIDs()
> would provide that information, but I don't know how to use that. If
> someone points me in the right
> direction I can add that as well.

I'm not yet ready to answer that.

Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Thomas Kellerer 2016-07-28 05:37:53 Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Previous Message Thomas Kellerer 2016-07-27 19:19:52 Re: ResultSet.getClob() causing problems when used with JPA's @Lob