You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Guillaume Chauvet (JIRA)" <ji...@apache.org> on 2013/09/26 16:20:02 UTC

[jira] [Commented] (OPENJPA-2430) Derby LOB persistence

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

Guillaume Chauvet commented on OPENJPA-2430:
--------------------------------------------

Maybe the ticket OPENJPA-2344 can help you ?
                
> Derby LOB persistence
> ---------------------
>
>                 Key: OPENJPA-2430
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2430
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 2.2.2
>         Environment: Java 1.6u45 (Java 1.7 and 1.8 EA versions seemed to have issues:
> Exception in thread "main" java.lang.LinkageError: loader (instance of  sun/misc/Launcher$AppClassLoader): attempted  duplicate class definition for name: "org/apache/openjpa/jdbc/identifier/DBIdentifier$DBIdentifierType"
>      [java] 	at java.lang.ClassLoader.defineClass1(Native Method)
>            Reporter: Dag H. Wanvik
>
> Derby is not listed among data bases that support LOB member fields, cf.
> The OpenJPA manual for version 2.2.2, section 7.7.11 LOB Streaming.
> See also the issue experienced by a user here: https://issues.apache.org/jira/browse/DERBY-6341
> I found that by overloading getLobField in DerbyDictionary (effectively materializing the LOB) I could make the user's example work. Cf. the code shown here:
> https://issues.apache.org/jira/browse/DERBY-6341?focusedCommentId=13777419&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13777419
> Would adding this overload be a possible way forward for the Derby support? I'm willing to make a proper patch if so.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira