Re: Timestamp changes committed to HEAD

On Mon, 1 Aug 2005, Oliver Jowett wrote:

> I've committed my Timestamp/Date/Time changes to CVS HEAD.

The regression tests fail on 7.2 and 7.3 with the below stacktrace.  I
understand that we may not be able to achieve 100% correctness with
7.2/7.3, but aren't there at least certain cases that work?

     [junit] Testcase: testSetTimestamp(org.postgresql.test.jdbc2.TimezoneTest):    Caused an ERROR
     [junit] ERROR:  Bad time external representation '2005-01-01 13:00:00.000000 +0100'
     [junit] org.postgresql.util.PSQLException: ERROR:  Bad time external representation '2005-01-01 13:00:00.000000
+0100'
     [junit]     at org.postgresql.core.v2.QueryExecutorImpl.receiveErrorMessage(QueryExecutorImpl.java:542)
     [junit]     at org.postgresql.core.v2.QueryExecutorImpl.processResults(QueryExecutorImpl.java:466)
     [junit]     at org.postgresql.core.v2.QueryExecutorImpl.execute(QueryExecutorImpl.java:364)
     [junit]     at org.postgresql.core.v2.QueryExecutorImpl.execute(QueryExecutorImpl.java:258)
     [junit]     at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:430)
     [junit]     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:346)
     [junit]     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:300)
     [junit]     at org.postgresql.test.jdbc2.TimezoneTest.testSetTimestamp(TimezoneTest.java:310)

Kris Jurka