The following bug has been logged online: Bug reference: 5747 Logged by: Kurt Stam Email address: ks...@apache.org PostgreSQL version: 8.3 Operating system: OSX Description: TimeStamps too far into the future are invalid Details:
https://issues.apache.org/jira/browse/JUDDI-374 When the coverage period goes out too far postgres has issues. The coverage periods are specified in the uddi-tck-base module in the directory src/main/resources/uddi_data/subscription; the files subscriptionresults3.xml and subscriptionresults4.xml: Changing the endPoint from 2100 to 2030. This is clearly a bug in postgres or the postgres driver. On saving no error is thrown, however the endpoint field is set to 'invalid' which is an issue when the date is parsed back into a timedate. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
