Eclipse Community Forums: EclipseLink » Re: Query field created by the @OrderColumn

Help

Home

Home » Eclipse Projects » EclipseLink » Re: Query field created by the @OrderColumn

Show: Today's Messages :: Show Polls :: Message Navigator

Re: Query field created by the @OrderColumn [message #778457]

Thu, 12 January 2012 15:19

Chris Delahunt

Messages: 1329
Registered: July 2009

Senior Member

By specifying the @OrderColumn(name = "MYORDER") on the OneToMany you are saying that the bList controls that field. I'm guessing that the error you get states that you have two writable fields, or is due to the field already existing.

If you are going to map the MYORDER field within the B object directly, you should be using the OrderBy on the collection instead of OrderColumn and maintain the collection order and the order field yourself.

Best Regards,
Chris

Report message to a moderator

Previous Topic:	Setting Cache expiry in persistance.xml
Next Topic:	QueryHints.LEFT_FETCH not working

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Sep 15 17:08:22 GMT 2019

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter