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

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Date: 2016-07-20 13:40:53
Message-ID: nmnv15$1dl$1@ger.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 resulting string.

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().

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Vladimir Sitnikov 2016-07-20 13:52:04 Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Previous Message Vladimir Sitnikov 2016-07-20 12:37:31 Re: ResultSet.getClob() causing problems when used with JPA's @Lob