Re: ResultSet.getClob() causing problems when used with JPA's @Lob - Mailing list pgsql-jdbc

From Thomas Kellerer
Subject Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Date
Msg-id nmnv15$1dl$1@ger.gmane.org
Whole thread Raw
In response to Re: ResultSet.getClob() causing problems when used with JPA's @Lob  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Responses Re: ResultSet.getClob() causing problems when used with JPA's @Lob  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Re: ResultSet.getClob() causing problems when used with JPA's @Lob  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
List pgsql-jdbc
Vladimir Sitnikov schrieb am 20.07.2016 um 14:37:
>>Is there anything new here?
>>This still doesn't work with 9.4.1208
>
> Nothing new here yet.
>
>>So we are caught between a rock and a hard place
>
> I feel your pain.
>
> Technically the problem is pgjdbc does not have "String -> Clob" conversion yet.
>
>>Are there any plans for this?
>
> I've not heard of those.
>
>>If not, is this something that would be accepted as a patch?
>
> I think so.
> It should be possible to check the result column type and create java.sql.Clob instance that would just work off the
resultingstring. 

I don't think checking the column type is necessary (at least not for me).
If this option is enabled, then all calls to getClob() are simply "re-routed" to getString().



pgsql-jdbc by date:

Previous
From: Vladimir Sitnikov
Date:
Subject: Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Next
From: Vladimir Sitnikov
Date:
Subject: Re: ResultSet.getClob() causing problems when used with JPA's @Lob