openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Bauer (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1249) Rework Oracle LOB support
Date Mon, 09 Nov 2009 21:14:32 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeremy Bauer updated OPENJPA-1249:
----------------------------------

    Attachment: OPENJPA-1249_NullLobHandling.patch

Attaching patch which uses native Oracle methods to create a temporary lob if the lob returned
from the updateable result set is null.  It handles DBCP pooled connections (via reflection)
provided a custom DBCP property is set which provides access to the underlying connection.
 If pooled by some other means, an attempt is made to use the JDBC 4 unwrap method (via reflection)
to gain access to a native Oracle connection.

I tried using native streams with the most current V10 and V11 drivers to more neatly handle
working work around the need for using empty_[c,b]lob or temporary LOBs but had no success.
 I could have overlooked something though.

> 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
>         Attachments: OPENJPA-1249_NullLobHandling.patch
>
>
> 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.


Mime
View raw message