The server's DateStyle parameter was changed to ISO. The JDBC driver requires DateStyle to begin with ISO for correct operation #1080
Milestone
Comments
vlsi
added a commit
to vlsi/pgjdbc
that referenced
this issue
Jan 20, 2018
Default PostgreSQL configuration is DateStyle='iso, dmy', however just iso would be fine. Note: PostgreSQL prints DateStyle value in upper case, and toUpperCase was added just in case. fixes pgjdbc#1080
vlsi
added a commit
that referenced
this issue
Jan 21, 2018
Default PostgreSQL configuration is DateStyle='iso, dmy', however pgjdbc should not raise errors if DateStyle is just ISO Note: PostgreSQL prints DateStyle value in upper case, and toUpperCase was added just in case. fixes #1080
rhavermans
added a commit
to bolcom/pgjdbc
that referenced
this issue
Jul 13, 2018
Default PostgreSQL configuration is DateStyle='iso, dmy', however pgjdbc should not raise errors if DateStyle is just ISO Note: PostgreSQL prints DateStyle value in upper case, and toUpperCase was added just in case. fixes pgjdbc#1080
rhavermans
added a commit
to bolcom/pgjdbc
that referenced
this issue
Jul 13, 2018
Default PostgreSQL configuration is DateStyle='iso, dmy', however pgjdbc should not raise errors if DateStyle is just ISO Note: PostgreSQL prints DateStyle value in upper case, and toUpperCase was added just in case. fixes pgjdbc#1080
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello and thank you for developing this software.
There seems to be a bug in the version 42.2.0.jre7 though:
I use Jetty 9.4.7 on CentOS 7.4 with PostgreSQL 9.6.6 with pgbouncer and postgresql-jdbc-4.2.0:
I run a WAR file in Jetty, compiled as following:
When I change the last line to
<pgsql.version>42.2.0.jre7</pgsql.version>
and recompile my WAR-file, then the Java code -throws an exception:
However I do have datestyle setting in my postgresql.conf:
datestyle = 'iso, mdy'
and I can see it at the console:
I.e. my datestyle setting (unchanged from stock installation) does begin with "ISO" as the exception wants it too.
The text was updated successfully, but these errors were encountered: