Vladimir Sitnikov

If only we could run full hibernate test suite against new version of pgjdbc. I don't have a test in mind, however I expect that kind of change might confuse...

@vladmihalcea , @lukaseder , here's the kind of the issues I want to avoid: #639 Here's rather innocent PR: https://github.com/pgjdbc/pgjdbc/pull/610/files It breaks existing applications since ORMs analyze `Types.OTHER` vs `Types.STRING`,...

>I don't think that this change is going to break the flow for reading/writing the timestamp value @vladmihalcea I believe this code will change its behavior: https://github.com/hibernate/hibernate-orm/blob/0a2a5c622e3eb30724e80bc8661c0ac55ebfb2be/hibernate-core/src/main/java/org/hibernate/loader/custom/JdbcResultMetadata.java#L67 Do you still...

Let me clarify a bit: pgjdbc's support of JDBC 4.2 was backward-compatible more-or-less. For instance, it has fancy java.time API support, however it was not the case that the same...

> if you return `Types.OTHER` for `TIMESTAMP` @vladmihalcea , what if `Types.TIMESTAMP_WITH_TIMEZONE` is returned for timestamptz column? Do native queries break?

>can't imagine this changes anything from the driver POV ? It might surface new bugs in the backend. The bugs might easily be "server-prepared-statement specific". I do not think we...

#1102 is the most popular pgjdbc page: The third one is https://github.com/pgjdbc/pgjdbc/issues/986

Just in case, here's a "discussion" in pgsql-hackers on absence of CLOB at the database level: https://www.postgresql.org/message-id/CAB=Je-EN_Wc-SURAfUAgzLh-kcmxD_migPaO1Jx+SksTAMEuog@mail.gmail.com

not yet

Current code does not look something I would be eager to push. I'm afraid I've no time to review it at the moment :(