I coded 2 options for a master detail relationship using DOA components.
The first option used bind variables and a master table that was used to drive iterating through the detail tables. The variables were set programatically and then Open was executed on the DOA dataset.
The second option was to set the master table property along with the detail fields and master fields in the master and detail datasets.
Doing a SQL Trace in Oracle had some surprising results. The master table iterated thru 68 records while the detail tables went thru 136 rows when using the Master Detail properties of the dataset.
Strangely, the programtic option produced only 68 rows for each of the detail queries executed according to the trace.
So, my question, why does using the properties to set the master-detail relationship cause twice the amount of rows to be returned compared to a programtic solution?
Thanks,
Bill K
The first option used bind variables and a master table that was used to drive iterating through the detail tables. The variables were set programatically and then Open was executed on the DOA dataset.
The second option was to set the master table property along with the detail fields and master fields in the master and detail datasets.
Doing a SQL Trace in Oracle had some surprising results. The master table iterated thru 68 records while the detail tables went thru 136 rows when using the Master Detail properties of the dataset.
Strangely, the programtic option produced only 68 rows for each of the detail queries executed according to the trace.
So, my question, why does using the properties to set the master-detail relationship cause twice the amount of rows to be returned compared to a programtic solution?
Thanks,
Bill K
