Performance issue on Query Object when using Outer Join with more than one Child Table


Problem:
Sub-optimal
SQL (multiple SQL statements) generated when a query object has more than one child table in the data
sources nested directly under the parent table.

Resolution:
Change
the default “fetch mode” from “1:n” to “1:1” while linking the child
data sources to the parents.

Comments (0)