| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Cc: | Jorge Solórzano <jorsol(at)gmail(dot)com> |
| Subject: | Re: pgjdbc 42.1.0 release: changelog update |
| Date: | 2017-05-05 11:27:47 |
| Message-ID: | CAB=Je-E-Qh-CHcRZdDHTFb4eMTmCoGoSaQZULnT16cHdmd0ixw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Just an update: I'm running into a timestamp issue while releasing
42.1.0.jre6.
The bug is: [INFO] TimestampTest.testInfinity:122->runInfinityTests:154
expected:<[infinity]> but was:<[5881610-07-11]>
I'm going to fix that, and proceed with 42.1.1, 42.1.1.jre7, 42.1.1.jre6.
As far as I understand, the fix is to move guessTimestamp after "if
(infinity)" checks:
https://github.com/pgjdbc/pgjdbc/blob/f375701b571c308b7e389df49c1d958f416e4340/pgjdbc/src/main/java/org/postgresql/jdbc/TimestampUtils.java#L835-L841
Note: there are bits of 42.1.0 published to Maven Central (jre8 and jre7
builds), however there will never be 42.1.0.jre6.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2017-05-05 20:43:58 | [pgjdbc/pgjdbc] 1e5bf5: fix: infinite dates might be corrupted when transf... |
| Previous Message | Vladimir Sitnikov | 2017-05-04 21:02:47 | [pgjdbc/pgjdbc] 448276: [maven-release-plugin] prepare for next developmen... |