Just an update on this. I've attached a test case which reproduces
the issue.
In ABean if you change the field from 'C' to 'c' the test fails. It
seems anything that sorts before 'b' in the ASCII chart will work and
anything after 'b' will fail.
I saw this exact thing in the custom id issue. I suspect there might
be one of those "anywhere we do x, we need to fix it" kind of issues
where x is some sort of collection usage that results in order making
a difference.
-David
On Feb 10, 2009, at 2:11 PM, Kevin Sutter wrote:
Thanks for doing this, Don! Always good to enhance our test bucket.
Kevin
On Tue, Feb 10, 2009 at 3:55 PM, Donald Woods (JIRA)
<[email protected]>wrote:
[
https://issues.apache.org/jira/browse/OPENJPA-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672417
#action_12672417]
Donald Woods commented on OPENJPA-919:
--------------------------------------
BTW - these tests prove that OpenJPA is handling null relationships
correctly, as tested for in the EJB TCK...
JUnit for Bi-directional OneToOne with null relationships
---------------------------------------------------------
Key: OPENJPA-919
URL: https://issues.apache.org/jira/browse/
OPENJPA-919
Project: OpenJPA
Issue Type: Improvement
Components: jdbc
Affects Versions: 1.2.0, 1.3.0, 2.0.0
Reporter: Donald Woods
Priority: Trivial
Fix For: 1.2.1, 1.3.0, 2.0.0
Attachments: OPENJPA-919-branches12x.patch,
OPENJPA-919-branches13x.patch, OPENJPA-919-trunk.patch
Testcase to verify relationships in a bi-directional OneToOne are
null
(as tested for by the EJB TCK) when:
1) the relations are not set (should default to null)
2) the relations are explicitly set to null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
