[teiid-issues] [JBoss JIRA] (TEIID-5817) zero precision loaded for java.sql.Timestamp
[
https://issues.jboss.org/browse/TEIID-5817?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5817.
-----------------------------------
Fix Version/s: 13.0
12.3.1
Assignee: Steven Hawkins
Resolution: Done
Went ahead and addressed both the parsing changes and the odata issue. In short the jdbc
metadata and Teiid uses timestamp precision to mean the full width of the string. 19
characters + . + up to 9 fractional digits, so the effective default for Teiid is 29. The
scale of a timestamp is meant to capture just the number of fractional seconds. On our
metadata objects if both values are 0, then it's assume that we're using the
default values.
All of the changes were backported to 12.3.x. I'll look at bringing at least the
odata change to 12.2.x
zero precision loaded for java.sql.Timestamp
--------------------------------------------
Key: TEIID-5817
URL: https://issues.jboss.org/browse/TEIID-5817
Project: Teiid
Issue Type: Bug
Components: OData, Query Engine
Reporter: Renat Eskenin
Assignee: Steven Hawkins
Priority: Major
Fix For: 13.0, 12.3.1
Attachments: image-2019-09-20-13-30-58-536.png,
image-2019-09-20-13-34-56-255.png
I create spring-boot project for translate jdbc connection from vertica JDBC to odata4
REST interface.
Base project is spring-odata-example in teiid git.
When i get request to object with field witch Timestamp type i get the exception:
Request:
GET /vertica-odata-facade/odata/vertica/domain?%24top=1
Response:
{
"error": {
"code": null,
"message": "The value '2019-09-12 09:26:22.323764' is not
valid for property 'created_date'."
}
}
This field in vertica
!image-2019-09-20-13-34-56-255.png|thumbnail!
name: created_by_id
type: Timestamp
column size: 26
decimal digits: 6
--
This message was sent by Atlassian Jira
(v7.13.8#713008)