[
https://issues.apache.org/jira/browse/OPENJPA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abe White resolved OPENJPA-162.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.9.7
Fixed in revision 514847. Test case TestIdOrderedOneMany added.
> @OrderBy on @OneToMany does not allow ordering by @Id value
> -----------------------------------------------------------
>
> Key: OPENJPA-162
> URL: https://issues.apache.org/jira/browse/OPENJPA-162
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 0.9.6
> Environment: Using PostgreSQL 8.1 as the database
> Reporter: Nick Johnson
> Fix For: 0.9.7
>
>
> Using the following annotation:
> @OneToMany(mappedBy="root", fetch=FetchType.LAZY)
> @OrderBy("objectId ASC")
> private List<Message> messages;
> I get the exception "Cannot order
> "net.spatula.tally_ho.model.MessageRoot.messages" on "objectId", because that
> field is not in the default fetch group. You can only order on fields that
> will be selected when the related object is loaded."
> I should certainly hope that the primary key of the related object is going
> to be selected when the object is loaded:
> @Id
> @Column(name = "object_id")
> private long objectId;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
