Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Re: Query field created by the @OrderColumn
Re: Query field created by the @OrderColumn [message #778457] Thu, 12 January 2012 10:19
Chris Delahunt is currently offline Chris Delahunt
Messages: 1017
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
Previous Topic:Setting Cache expiry in persistance.xml
Next Topic:QueryHints.LEFT_FETCH not working
Goto Forum:
  


Current Time: Fri Aug 22 07:54:18 EDT 2014

Powered by FUDForum. Page generated in 0.01613 seconds