Direct=true with TIMESTAMP WITH TIMEZONE timezone offset bug
Posted: Wed 05 Jan 2011 12:38
I have a table, MyTable, with a column, Timestamp, of type TIMESTAMP WITH TIMEZONE. The entity model generated from this assigns the DateTime type to the Timestamp property of MyTable. Unfortunately, the DateTime has no timezone offset information contained in it (as opposed to DateTimeOffset).
I have noticed different behaviour between Direct=True vs Direct=False.
I insert a MyTable entity with Timestamp set as follows, my timezone is GMT+1:
I get the following value for Timestamp in the database:
In Direct mode, shouldn't the DateTime assumed to be local time, like how the Oracle client handles it, or is this expected behaviour?
This causes problems for us because the data in the TIMESTAMP WITH TIMEZONE columns are different depending on whether Direct mode is true or false. The data should be the same no matter what mode I am using.
I am using Devart dotConnect for Oracle Professional 6.0.58.0.
I have noticed different behaviour between Direct=True vs Direct=False.
I insert a MyTable entity with Timestamp set as follows, my timezone is GMT+1:
Code: Select all
myTable.Timestamp = DateTime.Now;
- Direct=true (Direct mode): 05.01.11 13:19:40,732423 +00:00
Direct=false (Oracle client mode): 05.01.11 13:19:49,663316 +01:00
In Direct mode, shouldn't the DateTime assumed to be local time, like how the Oracle client handles it, or is this expected behaviour?
This causes problems for us because the data in the TIMESTAMP WITH TIMEZONE columns are different depending on whether Direct mode is true or false. The data should be the same no matter what mode I am using.
I am using Devart dotConnect for Oracle Professional 6.0.58.0.