openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henno Vermeulen <>
Subject RE: bug in openjpa with ordercolumn and mapped by
Date Fri, 18 Jul 2014 12:53:41 GMT
I wonder if this is related to the following bug I reported as
I could work around my bug by making the order column nullable @OrderColumn(nullable = true).
Perhaps it helps in your case as well.


-----Oorspronkelijk bericht-----
Van: Rick Curtis [] 
Verzonden: vrijdag 18 juli 2014 14:43
Onderwerp: Re: bug in openjpa with ordercolumn and mapped by

Michael -

I browsed through your previous post and it certainly looks like a bug.
Please go ahead and open a JIRA.  If you're feeling particularly courageous, you could always
try to format your github project into a 'proper' OpenJPA junit test[1]. I'm not going to
promise that I'll get time to look at it in the coming days, but getting a JIRA opened will
get things rolling in the right direction.



On Fri, Jul 18, 2014 at 4:50 AM, Michael Wiles <>

> So I've found some behaviour I didn't expect.
> If I use orderColumn  on a one to many it works fine. I see the order 
> column being updated. This is for a uni directional relationship.
> If I however add a mappedBy to make it bidirectional the order column 
> no longer gets updated.
> I assume there's no other reason by bidirectional relationships and 
> order column shouldn't work. If I try it with another jpa provider it 
> does work (Eclipselink).
> I have created a github project to demonstrate...
> see
> --
> see my blog:

*Rick Curtis*

View raw message