Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is the result of reading a TIMESTAMP WITH TIME ZONE different?

April 26, 2017different Reading time TIMESTAMP zone

0

Posted

Why is the result of reading a TIMESTAMP WITH TIME ZONE different?

1 Answer

0

Posted

The old behavior was incorrect. See bug 4322830. The old behavior was to construct a Timestamp that would print the same value as the database value. But since Timestamp is in the UTC time zone this would give a Timestamp value that was offset from the correct value. 8:00am January 1, 2007 UTC is not the same as 8:00am January 1, 2007 PST. They represent different points in time. If you read 8:00am January 1, 2007 PST in the database, the 9i and 10g drivers would construct a Timestamp with the value 8:00am January 1, 2007 UTC. This value would print “correctly”, that is it would print as “8:00am January 1, 2007”, but it obviously represented the wrong instant in time. The 11.1 drivers fix this bug.