[
https://issues.jboss.org/browse/TEIIDSB-118?page=com.atlassian.jira.plugi...
]
Renat Eskenin edited comment on TEIIDSB-118 at 9/20/19 1:10 PM:
----------------------------------------------------------------
1, 2. Ok, string representation length. I did not check jdbc spec, tnx :) But in ddl
generation/parsing (step 2) we have wrong ddl generated by jdbc metadata, because we have
zero precision, not just default (buggy 4 value).
3. So, may be default value is 19
https://docs.oracle.com/javase/8/docs/api/java/sql/Timestamp.html
was (Author: i3draven):
1, 2. Ok, string representation length. I did not check jdbc spec, tnx :) But in ddl
generation/parsing (step 2) we have wrong ddl generated by jdbc metadata, because we have
zero precision, not just default (buggy 4 value).
3. So, may be default value is 19 or 20
https://docs.oracle.com/javase/8/docs/api/java/sql/Timestamp.html
zero precision loaded for java.sql.Timestamp
--------------------------------------------
Key: TEIIDSB-118
URL:
https://issues.jboss.org/browse/TEIIDSB-118
Project: Teiid Spring Boot
Issue Type: Bug
Components: datasource, OData
Affects Versions: 1.2.0
Reporter: Renat Eskenin
Priority: Major
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)