Re: ResultSet.getClob() causing problems when used with JPA's @Lob
От | Thomas Kellerer |
---|---|
Тема | Re: ResultSet.getClob() causing problems when used with JPA's @Lob |
Дата | |
Msg-id | nmnv15$1dl$1@ger.gmane.org обсуждение исходный текст |
Ответ на | 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
Re: ResultSet.getClob() causing problems when used with JPA's @Lob |
Список | 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 по дате отправления: