vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The following bug has been logged online: Bug reference: 1525 Logged by: François LECOMTE Email address: francois.lecomte@oosphere.com PostgreSQL version: 8.0.1 Operating system: Linux Debian Description: wrong time when getting timestamp from date field Details: Problem when getting a Java Timestamp object on a DATE database field. With driver pg74jdbc3.jar : hours, minutes, seconds and millis have zero values (ex : "2003-09-10 00:00:00.0") in the Timestamp object, no problem. With driver postgresql-8.0-310.jdbc3.jar (same database, same table, same record) : we get 1 hour and zero minutes, seconds and millis ! ("2003-09-10 01:00:00.0") Maybe UTC time ? but suerly a bug... ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| ||||
| On Fri, 4 Mar 2005, François LECOMTE wrote: > Bug reference: 1525 > PostgreSQL version: 8.0.1 > Description: wrong time when getting timestamp from date field > > Problem when getting a Java Timestamp object on a DATE database field. > With driver pg74jdbc3.jar : hours, minutes, seconds and millis have zero > values (ex : "2003-09-10 00:00:00.0") in the Timestamp object, no problem. > With driver postgresql-8.0-310.jdbc3.jar (same database, same table, same > record) : we get 1 hour and zero minutes, seconds and millis ! ("2003-09-10 > 01:00:00.0") > Maybe UTC time ? but suerly a bug... > There is a known bug in the 8.0 jdbc driver when the client and server are in different timezones. Is that the case here? Kris Jurka ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org |
| Thread Tools | |
| Display Modes | |
|
|