[jira] [Commented] (OLINGO-329) Not all JPA data types handled correctly

["Chandan V.A (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OLINGO-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046856#comment-14046856 ] 

Chandan V.A commented on OLINGO-329:
------------------------------------

Hello Rudy,
java.sql.Timestamp is now supported with commit - http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/9b6e92a6 

Can you please check.
Secondly Boolean data type was already supported in release 1.2.0. Can you please explain how you are getting a byte data type for Boolean.

Thanks
Kind regards
Chandan

> Not all JPA data types handled correctly
> ----------------------------------------
>
>                 Key: OLINGO-329
>                 URL: https://issues.apache.org/jira/browse/OLINGO-329
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: V2 1.2.0
>            Reporter: Rudy Gardelein
>            Assignee: Chandan V.A
>             Fix For: V2 2.0.0
>
>
> As described in the following link (http://scn.sap.com/community/gateway/blog/2014/02/05/odata-producer-using-apache-olingo-with-mysql-jpa-tomcat-web-server)  there are issues with the correct translation of JPA data types boolean and timestamp in version V2 1.2 of Olingo.
> Boolean datatype is translated to Java byte type.  Timestamp is translated to Java timestamp.  Both of these however do not work in the Odata service as generated by Olingo.
> Raising this issue as suggested by Chandan V.A. from SAP.



--
This message was sent by Atlassian JIRA
(v6.2#6252)