Feedback
Did this article resolve your question/issue?

   

Article

Queries to Oracle Service Cloud DELETEDTIME column always return results in the GMT timezone

Information

 
TitleQueries to Oracle Service Cloud DELETEDTIME column always return results in the GMT timezone
URL NameQueries-to-Oracle-Serivce-Cloud-DELETEDTIME-column-always-return-results-in-the-GMT-timezone
Article Number000180548
EnvironmentProduct: Connect for ODBC Oracle Service Cloud driver
Version: 7.1
OS: All supported platforms
Database: Oracle Service Cloud
Application: All supported applications
Question/Problem Description
Queries to Oracle Service Cloud, the DELETEDTIME column while connecting with the Connect for ODBC Oracle Service Cloud driver always return results in the GMT timezone
Steps to Reproduce
Clarifying Information
Expect time results to be returned in the local client timezone.
Error Message
Defect Number
Enhancement Number
Cause
Resolution
The Oracle Service Cloud database is not reporting the datatype correctly. The metadata for the DELETETIME column is reporting "STRING" where it should be reporting "DATETIME". The driver is not going to convert a string to the local client timezone.

Contact Oracle to get additional information on this issue.
Workaround
Notes
Last Modified Date2/3/2017 4:14 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.