TIMESTAMP WITH TIMEZONE daylight savings bug
Posted: Tue 29 Mar 2011 09:00
I have an application that records 2 timestamps in a table, both columns are of type TIMESTAMP WITH TIMEZONE.
The first column, APP_RECEIVE_TIME, is set by our .NET application.
The second column, DB_INSERT_TIME, is set by our database via the column's default value.
After the daylight savings time switch-over, I found that the APP_RECEIVE_TIME was incorrect. It contained the local time with the wrong offset value. The expected offset value was +02:00.
Example:
APP_RECEIVE_TIME: 28-MAR-11 05.03.53.226108 PM +01:00
DB_INSERT_TIME: 28-MAR-11 05.03.54.277826 PM +02:00
I would like to note that I am using Direct=true, because I have previously run into a bug with TIMESTAMP WITH TIMEZONE and Direct=true (http://www.devart.com/forums/viewtopic.php?t=19911).
This problem has been observed in dotConnect for Oracle 6.10.96.0.
Edit
We tested with Direct=false (with Oracle Client), and the offset is set correctly. The problem only occurs with Direct=true.
The first column, APP_RECEIVE_TIME, is set by our .NET application.
The second column, DB_INSERT_TIME, is set by our database via the column's default value.
After the daylight savings time switch-over, I found that the APP_RECEIVE_TIME was incorrect. It contained the local time with the wrong offset value. The expected offset value was +02:00.
Example:
APP_RECEIVE_TIME: 28-MAR-11 05.03.53.226108 PM +01:00
DB_INSERT_TIME: 28-MAR-11 05.03.54.277826 PM +02:00
I would like to note that I am using Direct=true, because I have previously run into a bug with TIMESTAMP WITH TIMEZONE and Direct=true (http://www.devart.com/forums/viewtopic.php?t=19911).
This problem has been observed in dotConnect for Oracle 6.10.96.0.
Edit
We tested with Direct=false (with Oracle Client), and the offset is set correctly. The problem only occurs with Direct=true.