Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-710

Unordered collection field adds ORDER BY clause

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.2.0, 1.2.1, 1.3.0
    • Fix Version/s: 1.0.4, 1.2.0, 1.2.1, 1.3.0
    • Component/s: kernel
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              ppoddar@apache.org Pinaki Poddar
              Reporter:
              ppoddar@apache.org Pinaki Poddar
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: