Example of How the Entity Relationship Designer Filters Links and Joins

Example of How the Entity Relationship Designer Filters Business Components describes an example ERD that includes two entities and one relationship. Assume you bind entities A and C to business components and that you must bind the relationship AC to a link or join. The Entity Relationship Designer filters the list of links and joins that are available for binding that the context described in the ERD requires.

The following table describes the links and joins that are available to bind to relationship AC.

Relationship AC Objects That Are Available to Bind

one-to-many

The following objects are available to bind:

  • A join whose source is the business component that is bound to Entity C, and whose destination is the primary table of the business component that is bound to Entity A.

  • A link between the business component that is bound to Entity A and the business component that is bound to Entity C, where the business component bound to Entity A is the parent and the business component bound to Entity C is the child.

many-to-one

The following objects are available to bind:

  • A join whose source is the business component that is bound to Entity A to the primary table of the business component that is bound to Entity C.

  • A link between the business component that is bound to Entity C and the business component that is bound to Entity A, where C is the parent and A as the child.

many-to-many

A link between business components that are bound to Entities A and C is available to bind.