[
https://issues.apache.org/jira/browse/OLINGO-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918008#comment-13918008
]
Chandan V.A commented on OLINGO-185:
------------------------------------
Hi Carl,
I would like to go with the annotation "@Lob" as specified in the JPA
specification for generating Large and Binary object rather than going with the
data type "Clob.class".
The idea is as follows.
A) Look for the annotation "@Lob" on the JPA entity property.
B) If the annotation is present and the data type for the JPA entity property
is a string or character or character array type then keep it as Edm.string
type ELSE
C) if the annotation is present and the data type for the JPA entity property
is NOT a string or character or character array type then keep it as
Edm.binary. DONT check for any specific data type like Clob.class as it might
tie up the OData 2 JPA processor to a specific implementation of JPA
specification.
D) if a JPA entity property has the data type as Clob.class but is not
annotated with "@Lob" then that property will be ignored by OData 2 JPA
processor.
Can you please comment on this proposal.
Regards
Chandan
> support for Clob
> ----------------
>
> Key: OLINGO-185
> URL: https://issues.apache.org/jira/browse/OLINGO-185
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-jpa
> Affects Versions: V2 1.2.0
> Reporter: Carl J. Mosca
> Priority: Blocker
> Labels: blob, clob, jpa
> Attachments:
> org.apache.olingo.odata2.jpa.processor.core.access.model.JPATypeConverter.java.diff
>
>
> support for Clob (other BLOB types?) We have successfully processed these as
> String type
--
This message was sent by Atlassian JIRA
(v6.2#6252)
