[teiid-issues] [JBoss JIRA] (TEIIDSB-118) zero precision loaded for java.sql.Timestamp

[Steven Hawkins (Jira)]

    [ https://issues.jboss.org/browse/TEIIDSB-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787538#comment-13787538 ] 

Steven Hawkins commented on TEIIDSB-118:
----------------------------------------

> So, may be default value is 19 https://docs.oracle.com/javase/8/docs/api/java/sql/Timestamp.html

The effective default in terms of string length is 29.

> And, its so strange behavior if precision is string representation length...for odata4

That is not intended and will be corrected with this issue.

> 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)