Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Works as designed
    • Labels:
      None

      Description

      Quite happy to see jpa 2.1 is near...

      I couldn't seem to subscribe to the mailing list, so here are some comments.

      Some minor question/suggestion, maybe already discussed?

      Why do we have this:

      CriteriaQuery<T> where(Predicate... restrictions);

      But not, additionnally, this:

      CriteriaQuery<T> where(List<Predicate> restrictions);

      While there is:

      CriteriaQuery<T> groupBy(Expression<?>... grouping);
      and
      CriteriaQuery<T> groupBy(List<Expression<?>> grouping);

      And List parameters for having, orderBy, ...

        Activity

        Hide
        ldemichiel added a comment -

        It was felt that CriteriaQuery<T> where(List<Predicate> restrictions)
        was not needed, as unlike in the other cases, there are operations to
        combine expressions using the logical operators.

        You can post to the users email list by joining the project.

        Show
        ldemichiel added a comment - It was felt that CriteriaQuery<T> where(List<Predicate> restrictions) was not needed, as unlike in the other cases, there are operations to combine expressions using the logical operators. You can post to the users email list by joining the project.

          People

          • Assignee:
            Unassigned
            Reporter:
            ymajoros
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: