[
https://issues.apache.org/jira/browse/OPENJPA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter updated OPENJPA-710:
---------------------------------
Affects Version/s: 1.3.0
1.2.1
1.1.1
1.0.4
1.0.0
1.0.1
1.0.2
1.0.3
1.1.0
1.2.0
Fix Version/s: 1.2.1
1.1.1
1.0.4
Added additional versions (both affects and fix).
> Unordered collection field adds ORDER BY clause
> -----------------------------------------------
>
> Key: OPENJPA-710
> URL: https://issues.apache.org/jira/browse/OPENJPA-710
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.1.1, 1.2.0,
> 1.2.1, 1.3.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 1.0.4, 1.1.1, 1.2.1, 1.3.0
>
>
> An ORDER BY clause is added while selecting even for collection-valued fields
> that do not require ordering.
> For example, consider a typical Parent-Child model with bi-directional
> relationship where Parent.children is declared and/or initialized as a Set
> rather than a List will result in the following SQL
> "SELECT t0.id, t0.name, t1.id FROM PARENT t0 LEFT OUTER JOIN CHILD t1
> ON t0.id = t1.PARENT_ID ORDER BY t1.PARENT_ID"
> corresponding to JPQL "select p from Parent p left join fetch p.children".
> Is ORDER BY clause necessary in this context? I
> t also adds an extra performance overhead on the SQL query execution for a
> fairly frequent usage pattern.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
