[
https://issues.apache.org/jira/browse/OPENJPA-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milosz Tylenda updated OPENJPA-525:
-----------------------------------
Attachment: OPENJPA-525.3.patch
Albert, could you apply the attached OPENJPA-525.3.patch to trunk and see
whether it works for you? With that patch TestSerializedLobs.testNullableClob
passes with Oracle.
I have moved the call to translate method from AbstractResult.getObject to
ResultSetResult.getObjectInternal. Now ResultSetResult.getObjectInternal
receives a Column instead of a bare Number and can determine if the Coulmn is
of type CLOB.
> Inserts new entity with NULL value for Clob column actually inserts empty
> string
> --------------------------------------------------------------------------------
>
> Key: OPENJPA-525
> URL: https://issues.apache.org/jira/browse/OPENJPA-525
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.0.2, 1.1.0, 2.0.0
> Environment: OpenJPA 1.0.0, 1.0.2
> Oracle XE 10g (JDBC driver 10.2.0.3.0
> JRE 1.5.0_13
> Reporter: Frank Le
> Assignee: Milosz Tylenda
> Fix For: 1.1.1, 2.0.0
>
> Attachments: OPENJPA-525.2.patch, OPENJPA-525.3.patch,
> OPENJPA525.patch, OPENJPA525_1_1_x.patch
>
>
> Inserts new entity with NULL value for Clob column with "nullable = true"
> actually inserts empty string as the value!
> Here's the persistence class:
> public class Exam... {
> @Lob
> private String text;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
