Difference between revisions of "EclipseLink/DesignDocs/312146"

From Eclipsepedia

Jump to: navigation, search
(Requirements)
(Requirements)
Line 86: Line 86:
 
* Support JPA 2.1 ON clause
 
* Support JPA 2.1 ON clause
 
* Support JPA 2.1 function key word
 
* Support JPA 2.1 function key word
 +
* Allow sub-selects in the select clause, having clause, and from clause. ("optionalish" in JPA 2.1)
  
 
= Design Constraints =
 
= Design Constraints =

Revision as of 11:26, 6 February 2012

Design Specification: Enhanced JPQL

ER 312146

Feedback

Document History

Date Author Version Description & Notes
2011-10-04 James 0.1 Draft

Project overview

JPQL currently offers a sub-set of SQL functionality. Some queries that are possible using SQL cannot be defined using JPQL.

It is desired to make EclipseLink's JPQL support be more complete of what is possible in SQL.

A key requirement from users (#1 voted enhancement) is to have ON clause support in JPQL.

Other missing features of SQL could also be added to JPQL, such as sub selects in the SELECT from FROM clauses, and enhanced function support.

Other JPQL enhancements:

Other JPQL bugs:

Concepts

ON clause : the SQL clause part of the FROM clause that defines how to tables are joined, this can be used for both joins and outer joins, but is required for outer joins.

outer join : A join where if a row in the source table has no joined rows in the target table it is still included in the join result with a null row for the target table.

ANTRL : Third party library currently used in EclipseLink for parsing JPQL.

SQL : SQL 2003 BNF

Hermes : New JPQL parser developed by Dali project for parsing JPQL at design time. Currently included in EclipseLink SVN, but not currently used.

Requirements

  • Support additional ON clause for a relationship join.
  • Support an ON clause on the join for two independent objects.
  • Support JPA 2.1 ON clause
  • Support JPA 2.1 function key word
  • Allow sub-selects in the select clause, having clause, and from clause. ("optionalish" in JPA 2.1)

Design Constraints

  • Outer join capabilities differ in different databases.
  • SQL capabilities differ in different databases.

Functionality

  • Extend ObjectExpression to support an onClause, must normalize and copy expression accordingly.
  • Allow ExpressionBuilders and other Expressions to be added to nonFetchJoinExpressions in ObjectLevelReadQuery.
  • Add support for having SubSelectExpressions in SQLSelectStatement's fields and print/normalize accordingly.
  • Added new FromSubSelectExpression to allow SubSelectExpressions to be contained an aliased in a SQLSelectStatement's from clause.
  • Added new FromAliasExpression to allow get() to be used from a FromSubSelectExpression and treated as a QueryKeyExpression aliasing one of the items in the sub-select.
  • Added support to FunctionExpression and RelationExpression to support object comparisons with IN. For composite ids as parameters arrayed INs are used, this requires database specific support.
  • Added support for count distinct with composite ids for MySQL and supporting databases.

Testing

ON clause needs Expression tests in core testing and JPQL tests in JPA testing. Testing both 1-1, 1-m, relationship and parallel.

  • Added ON clause tests to Expression outerJoin core tests (both inner and outer joins tested).
  • Added FROM and SELECT sub-select tests to Expression subSelects core tests.

API

JPQL

  • ON
    • Select e from Employee e left join e.address a on (a.city = 'Ottawa')
    • Select e from Employee e left join Project p on (p.teamLeader = e)
  • Sub-select
    • Select e.id, (Select a.city from Address a where e.address = a) from Employee e
    • Select e.id, a2.city from Employee e, (Select a.city from Address a) a2
  • IN / NOT IN
    • Select e from Employee e where e.address in (Select a from Address a where city = 'Ottawa')
    • Select e from Employee e join e.phones p where p in :phones
    • Select e from Employee e join e.phones p where p in (:phone1, :phone2)
    • Select e from Employee e where e.address = (Select a from Address a where street = '27 Hastings')
  • ORDER BY (order by objects, Id or all fields for embeddables)
    • Select e from Employee e order by e.address
    • Select e from Employee e order by e.period

Native API

  • Expression
    • join(Expression target, Expression onClause)
    • leftJoin(Expression target, Expression onClause)
    • getAlias(Expression subSelect)
  • ObjectLevelReadQuery
    • addNonFetchJoin(Expression)

Examples:

// ON
ExpressionBuilder employee = new ExpressionBuilder();
Expression address = employee.getAllowingNull("address");
employee.leftJoin(address, address.get("city").equal("Ottawa"));
ReadAllQuery query = new ReadAllQuery(Employee.class, employee);
query.addNonFetchJoin(address);
 
// ON
ExpressionBuilder employee = new ExpressionBuilder(Employee.class);
ExpressionBuilder project = new ExpressionBuilder(Project.class);
employee.join(project, project.get("teamLeader").equal(employee));
ReadAllQuery query = new ReadAllQuery(Employee.class, employee);
query.addNonFetchJoin(project);
 
// SELECT SUB-SELECT
ExpressionBuilder employee = new ExpressionBuilder(Employee.class);
ExpressionBuilder address = new ExpressionBuilder(Address.class);
ReportQuery subQuery = new ReportQuery(Address.class, address);
subQuery.addAttribute("city");
subQuery.setSelectionCriteria(employee.get("address").equal(a));
ReportQuery query = new ReportQuery(Employee.class, employee);
query.addAttribute("id");
query.addItem("city", employee.subQuery(subQuery));
 
// FROM SUB-SELECT
ExpressionBuilder employee = new ExpressionBuilder(Employee.class);
ExpressionBuilder address = new ExpressionBuilder(Address.class);
ReportQuery subQuery = new ReportQuery(Address.class, address);
subQuery.addAttribute("city");
subQuery.setSelectionCriteria(employee.get("address").equal(a));
Expression a2 = employee.getAlias(employee.subQuery(subQuery));
ReportQuery query = new ReportQuery(Employee.class, employee);
query.addNonFetchJoin(a2);
query.addAttribute("id");
query.addItem("city", a2.get("city"));

Config files

Documentation

Need to document our BNF, example queries and support beyond JPA 2.0/2.1 in query section.

Open Issues

Issue # Owner Description / Notes
1 Which JPQL parser should be used ANTLR or Hermes?

Decisions

Issue Description / Notes Decision

Future Considerations

  • Other JPQL enhancements.
  • Criteria support.