You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Milosz Tylenda (JIRA)" <ji...@apache.org> on 2009/08/15 13:48:14 UTC
[jira] Commented: (OPENJPA-1249) Rework Oracle LOB support
[ https://issues.apache.org/jira/browse/OPENJPA-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743681#action_12743681 ]
Milosz Tylenda commented on OPENJPA-1249:
-----------------------------------------
Some posts from the users list more or less related:
http://n2.nabble.com/Oracle-Blob-Exception-with-11.1-jdbc-driver-td2242185.html#a2244553
http://n2.nabble.com/Oracle-blob-exception-td209885.html#a209886
http://n2.nabble.com/ClassNotFoundException-on-persisting-serialized-class-td2433282.html#a2437838
> Rework Oracle LOB support
> -------------------------
>
> Key: OPENJPA-1249
> URL: https://issues.apache.org/jira/browse/OPENJPA-1249
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 1.3.0, 2.0.0
> Reporter: Milosz Tylenda
> Priority: Minor
>
> We could probably get rid of the following Oracle-specific behaviour and code:
> - using non-embedded LOB handling when size of the value exceeds 4000 bytes/chars,
> - using empty LOB when persisting a null value.
> Chances are the above behaviour is not needed starting from Oracle 9 or 10.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.