Different handling of database timefields on insert and update
--------------------------------------------------------------
Key: GEOS-4486
URL: http://jira.codehaus.org/browse/GEOS-4486
Project: GeoServer
Issue Type: Bug
Components: PostGIS, WFS
Affects Versions: 2.0.2
Environment: Debian Squeeze , Tomcat-6.0.28-10, Lighttpd-1.4.28-3, postgis-1.5.1-5, postgresql-8.4.5-0squeeze2
Reporter: Karim Malhas
Assignee: Andrea Aime
Priority: Minor
Attachments: timefield.log, timefieldtable.sql
Given a Postgresql database containing a field of type:
time without time zone DEFAULT '00:00:00'::time without time zone
and JAVA_OPT to tomcat:
-Duser.timezone=Europe/Berlin
System time is UTC and the system timezone is set to Europe/Berlin as well
When inserting a feature with a field of value '00:00:00' the system/java timezone setting seems to be taken into account, and results in a database field of '01:00:00'.
Updating the same Feature with a field value of '00:00:00' again, sets the database field to '00:00:00'
The expectation was that both times the database-field would be set to '00:00:00'.
Workaround:
Setting the JAVA_OPT to:
-Duser.timezone=Europe/London
Does what I expected it to do.
Attached are a CREATE TABLE statement and logfiles showing the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira