[
https://issues.apache.org/jira/browse/OLINGO-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rudy Gardelein reopened OLINGO-329:
-----------------------------------
I have found another MySQL data type that is not supported: BigInteger.
Appreciate if you could provide some more details on how to annotate DB
specific datatypes (in this case MySQL) to make them recognized by the Olingo
JPA libary.There seem to be plenty of cases like this, so would save us time if
a generic approach to this can be described.
Thanks,
Rudy
> 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.3.4#6332)
