[
https://issues.apache.org/jira/browse/OPENJPA-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728854#action_12728854
]
Milosz Tylenda commented on OPENJPA-525:
----------------------------------------
Albert,
You don't run into problems with Derby and DB2 because LOB streaming requires
other databases (see AbstractLOBTest), otherwise it is basically a no-op.
Yes, the failing tests passed before the original patch although they were not
executed by the default test suite because of incorrect names.
For me, you can go ahead with the commit. I have little time this week and then
I start vacation. I will dig into this problem but probably no earlier than Jul
20.
> 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
> 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.
