[pgjdbc/pgjdbc] fcd1ea: fix: wrong results when a single statement isused... - Mailing list pgsql-jdbc

Branch: refs/heads/master
  Home:   https://github.com/pgjdbc/pgjdbc
  Commit: fcd1ea14545a113fe4a124e17132824e279f572e
      https://github.com/pgjdbc/pgjdbc/commit/fcd1ea14545a113fe4a124e17132824e279f572e
  Author: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
  Date:   2018-03-11 (Sun, 11 Mar 2018)

  Changed paths:
    M CHANGELOG.md
    M pgjdbc/src/main/java/org/postgresql/core/Oid.java
    M pgjdbc/src/main/java/org/postgresql/core/v3/QueryExecutorImpl.java
    M pgjdbc/src/main/java/org/postgresql/core/v3/SimpleQuery.java
    A pgjdbc/src/test/java/org/postgresql/core/OidToStringTest.java
    A pgjdbc/src/test/java/org/postgresql/core/OidValueOfTest.java
    M pgjdbc/src/test/java/org/postgresql/test/jdbc2/Jdbc2TestSuite.java
    M pgjdbc/src/test/java/org/postgresql/test/jdbc2/PreparedStatementTest.java

  Log Message:
  -----------
  fix: wrong results when a single statement is used with UNSPECIFIED types (#1137)

Timestamp, date (and some other types), are sent as UNSPECIFIED, and pgjdbc did not verify the actual parameter types
atparse time.
 
This might cause wrong results if the query was parsed with explicit type (e.g. setString(...)), and then re-executed
with
TIMESTAMP parameter (timestamps are sent as UNSPECIFIED, thus pgjdbc silently accepted the statement even though it
shouldreparse)
 

fixes #648
closes #674