Feedback
Did this article resolve your question/issue?

   

Article

DataDirect SQL Server JDBC driver always return String for DateTimeOffset

Information

 
TitleDataDirect SQL Server JDBC driver always return String for DateTimeOffset
URL Namedatadirect-sql-server-jdbc-driver-always-return-string-for-datetimeoffset
Article Number000153840
EnvironmentProduct: Connect for JDBC SQL Server Driver
Version : 5.1
OS: JAVA
Database : SQL Server
Application: All supported applications
Question/Problem Description
DataDirect SQL Server JDBC driver always return String for the data type DateTimeOffset.  Is it possible to map it to Timestamp instead?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
By default, DataDirect SQL Server JDBC driver return a String for the data type DateTimeOffset
Resolution
Set the connection parameter FetchTSWTZasTimestamp=true in the connection URL.

As per the product documentation, the data type datetimeoffset can be mapped to a VARCHAR or a TIMESTAMP depending on a flag.
When FetchTSWTZasTimestamp=false (default), this data type is mapped to the JDBC VARCHAR data type.
When FetchTSWTZasTimestamp=true, it is mapped to the JDBC TIMESTAMP data type.
Workaround
Notes
Last Modified Date4/16/2019 1:51 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.