We're updating the issue view to help you get more done. 

Allow LoadPlan building to determine whether an association attribute can be inner joined

Description

This relates back to and HHH-8980. The better solution to that scenario is to instead look at whether the attribute to be joined is declared on:

  1. The class being processed

  2. A super-class of the class being processed

  3. A sub-class of the class being processed

If declared on the class being processed, or one of its super-classes it is ok to use an inner join, provided that the attribute metadata says its ok (non-optional, etc). For cases where the attribute is declared on a sub-class of the class being processed, it is never going to be appropriate to use an inner join.

Environment

None

Status

Assignee

Unassigned

Reporter

Steve Ebersole

Components

Priority

Major