Re: ResultSet.getClob() causing problems when used with JPA's @Lob
| От | Vladimir Sitnikov |
|---|---|
| Тема | Re: ResultSet.getClob() causing problems when used with JPA's @Lob |
| Дата | |
| Msg-id | CAB=Je-FbszwjAFVYfr+DiGgS8dOhsOFTGK65=d7VyjPAHdnyvQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: ResultSet.getClob() causing problems when used with JPA's @Lob (Thomas Kellerer <spam_eater@gmx.net>) |
| Ответы |
Re: ResultSet.getClob() causing problems when used with JPA's @Lob
Re: ResultSet.getClob() causing problems when used with JPA's @Lob |
| Список | 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
В списке pgsql-jdbc по дате отправления: