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-20 12:37:31
Message-ID: CAB=Je-FBJgyP5xbpcBAVBc84k2YW82-T2zrYFaD-kBhoN1dFwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

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

Special thank would go for a patch that would add JPA -> pgjdbc kind of
integration test to the regression suite.

Vladimir

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Thomas Kellerer 2016-07-20 13:40:53 Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Previous Message Thomas Kellerer 2016-07-20 11:51:00 Re: ResultSet.getClob() causing problems when used with JPA's @Lob