Feedback
Did this article resolve your question/issue?

   

Article

Fractional seconds are coming as 0 in case of timestamp with timezone datatype with Connect for JDBC

Information

 
TitleFractional seconds are coming as 0 in case of timestamp with timezone datatype with Connect for JDBC
URL NameFractional-seconds-are-coming-as-0-in-case-of-timestamp-with-timezone-datatype-with-Connect-for-JDBC
Article Number000174845
EnvironmentProduct : Connect for JDBC
Version : 5.1
Database : Oracle
OS : All supported platforms
Application : Java
Question/Problem Description
Fractional seconds are coming as 0 for timestamp with timezone datatype.
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberDefect PSC00331404
Enhancement Number
Cause
Resolution
This is an expected behavior.
The scale is hard coded to 0 in the case when timestamp with timezone is returned and the value of FetchTSWTZ as Timestamp is false.
In this case, the column is treated as varchar and sets the scale as 0
.
 
Workaround
Notes
Last Modified Date12/7/2018 7:50 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.