[
https://issues.apache.org/jira/browse/OLINGO-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052263#comment-14052263
]
Chandan V.A commented on OLINGO-329:
------------------------------------
Hello Rudy,
The Olingo JPA processor relies on the JPA provider's (like Eclipse Link)
implementation with respect to data type handling and we have kept it free of
DB platform's native implementation of data types. So we will not be able to
provide a special handling for MySQL data types. However I can think of a
solution where you could annotate JPA attribute with type converters to convert
between Byte to Boolean. I hope this would solve your issue.
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)
