[
https://issues.apache.org/jira/browse/OPENJPA-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milosz Tylenda resolved OPENJPA-1691.
-------------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
The fix requires a JDBC 4 driver. There are still issues when querying over
long individual XML nodes coming from obscure limits in Oracle's extractValue()
function.
Note that reading XML values longer than 4000 bytes was also broken - replaced
getStringVal() calls with getClobVal().
As a side effect users gained a bit of control on INSERT/UPDATE statements in
DBDictionary.getMarkerForInsertUpdate method.
> Oracle XMLType column failed to insert/update when xml contains more than
> 4000 characters
> -----------------------------------------------------------------------------------------
>
> Key: OPENJPA-1691
> URL: https://issues.apache.org/jira/browse/OPENJPA-1691
> Project: OpenJPA
> Issue Type: Bug
> Components: sql
> Affects Versions: 1.2.2, 2.0.0, 2.0.1
> Environment: Oracle 10g, JDBC driver (ojdbc14.jar) 10.2.0.4.0,
> OpenJPA 1.2.2
> Reporter: Kelvin Law
> Assignee: Milosz Tylenda
> Fix For: 2.1.0
>
>
> Oracle throws the following exception when XML content is greater than 4000
> characters:
> ORA-01461: can bind a LONG value only for insert into a LONG column
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
