Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-4694

Query class does not handle distinct query properly

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 2.2.1.CR1
    • Fix Version/s: 2.3.0.ALPHA
    • Component/s: Framework
    • Labels:
      None

      Description

      With the update from 2.2.0.GA to 2.2.1.CR1 the SUBJECT_PATTERN within the Query class has changed. This pattern does filter this query as a bad one:

      select distinct bean1 from Bean1 bean1, Bean2 bean2 where bean1 in elements(bean2.bean1s) order by bean1.id asc

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  manaRH Marek Novotny
                  Reporter:
                  antibrumm Martin Frey
                • Votes:
                  3 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: