Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-M1
    • Component/s: query
    • Labels:
      None

      Description

      Implement according to Criteria API Spec.
      Iteration 1 will attempt an approach to convert QueryDefinition to a valid JPQL. This will help easier build-test-verify cycle.

      Iteration 1 may exclude SubQuery and Case statements.

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open In Progress In Progress
          6d 5h 14m 1 Pinaki Poddar 08/Dec/08 18:05
          In Progress In Progress Resolved Resolved
          9d 1h 47m 1 Pinaki Poddar 17/Dec/08 19:52
          Resolved Resolved Closed Closed
          446d 22h 38m 1 Donald Woods 09/Mar/10 18:31
          Donald Woods made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Donald Woods made changes -
          Fix Version/s 2.0.0-M1 [ 12313624 ]
          Due Date 2009-01-16 08:00:00.0 2009-01-16 00:00:00.0
          Pinaki Poddar made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          Hide
          Pinaki Poddar added a comment -

          The support for Criteria API as per the public draft version of JPA 2.0 specification is available.
          The basic approach reuses the existing kernel's capability to support JPQL by converting QueryDefinition to corresponding JPQL String, so the resultant JPQL string is executed as usual by the kernel.
          The JPA 2.0 Specification has not yet mandated any equivalence (string based or otherwise) between a QueryDefinition and a JPQL string. But an extended OpenJPAQueryBuilder provides such a conversion from a QueryDefinition to a JPQL string.
          The support is available for all constructs defined in Criteria API including new JPQL features such as KEY(), VALUE() or CASE statements. However, implementation of some of these new capabilities in the kernel's query engine is still in progress.

          Preliminary documentation has also been added. Due to the evolving status of the specification in this regard, the documentation mainly refers to the public draft version of the specification for details.

          Show
          Pinaki Poddar added a comment - The support for Criteria API as per the public draft version of JPA 2.0 specification is available. The basic approach reuses the existing kernel's capability to support JPQL by converting QueryDefinition to corresponding JPQL String, so the resultant JPQL string is executed as usual by the kernel. The JPA 2.0 Specification has not yet mandated any equivalence (string based or otherwise) between a QueryDefinition and a JPQL string. But an extended OpenJPAQueryBuilder provides such a conversion from a QueryDefinition to a JPQL string. The support is available for all constructs defined in Criteria API including new JPQL features such as KEY(), VALUE() or CASE statements. However, implementation of some of these new capabilities in the kernel's query engine is still in progress. Preliminary documentation has also been added. Due to the evolving status of the specification in this regard, the documentation mainly refers to the public draft version of the specification for details.
          Pinaki Poddar made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Pinaki Poddar made changes -
          Remaining Estimate 1,344h [ 4838400 ]
          Original Estimate 1,344h [ 4838400 ]
          Component/s query [ 12311309 ]
          Due Date 2009-01-16 00:00:00.0
          Jeremy Bauer made changes -
          Assignee Pinaki Poddar [ ppoddar@apache.org ]
          Jeremy Bauer made changes -
          Issue Type New Feature [ 2 ] Sub-task [ 7 ]
          Parent OPENJPA-800 [ 12409559 ]
          Pinaki Poddar made changes -
          Field Original Value New Value
          Link This issue is part of OPENJPA-773 [ OPENJPA-773 ]
          Pinaki Poddar created issue -

            People

            • Assignee:
              Pinaki Poddar
              Reporter:
              Pinaki Poddar
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1,344h
                1,344h
                Remaining:
                Remaining Estimate - 1,344h
                1,344h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Development