[
https://issues.apache.org/jira/browse/OPENJPA-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743688#action_12743688
]
Milosz Tylenda commented on OPENJPA-525:
----------------------------------------
To clarify: OpenJPA persists an empty CLOB (Oracle-specific) when value to be
persisted is null. Neither of the patches changes that. What the patches try to
do is when the empty CLOB is read back, it is detected that the CLOB is empty
and a null is returned. Without the patches, getString is called on the empty
CLOB which gives an empty string to the user.
Amy's patch fixes the issue (TestSerializedLobs.testNullableClob passes with
Oracle) but causes Albert's failure.
Albert's patch breaks the Oracle behaviour again
(TestSerializedLobs.testNullableClob fails with Oracle) but fixes the error
introduced by Amy's patch (so it is basically the state when no patch has been
applied in terms of functionality).
> 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, 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.
