1. The DSRequest has one attribute by the name of startRow. The first request that is fired has startRow=0 and the default batch size is 75 rows.
So the response contains 75 records. The consecutive DSRequest comes with startRow=75. Fetches another set of records starting from 75 to batchSize.
But the 3rd DSRequest that is fired has startRow=0 which force fetches the data from 0th row to 75 rows. Which results in the comboBox to blink continuosly.
2. Ideally the startRow attribute should be updated accordingly so that the records that are fetched are not repeated and thus do not cause re fetching of data,
thus avoiding the blinking of dropdown.
3. The efforts made in order to rectify this problem which did not work:
a) setting dataPageSize attribute to 25.
b) setting sqlPaging attribute to true.
c) Since the pagination fails after 2 requests, hence we set the batchSize = 1000. But for the cases where data is more than 1000 rows, it is still failing.
4. Also, the DSResponse is set adequately after each fetch operation, i.e.,
the endRow / startRow attributes are set adequately. Also the totalRows attributes are set accordingly.
The request is keep firing since it is unable to identify start and end rows properly.
So the response contains 75 records. The consecutive DSRequest comes with startRow=75. Fetches another set of records starting from 75 to batchSize.
But the 3rd DSRequest that is fired has startRow=0 which force fetches the data from 0th row to 75 rows. Which results in the comboBox to blink continuosly.
2. Ideally the startRow attribute should be updated accordingly so that the records that are fetched are not repeated and thus do not cause re fetching of data,
thus avoiding the blinking of dropdown.
3. The efforts made in order to rectify this problem which did not work:
a) setting dataPageSize attribute to 25.
b) setting sqlPaging attribute to true.
c) Since the pagination fails after 2 requests, hence we set the batchSize = 1000. But for the cases where data is more than 1000 rows, it is still failing.
4. Also, the DSResponse is set adequately after each fetch operation, i.e.,
the endRow / startRow attributes are set adequately. Also the totalRows attributes are set accordingly.
The request is keep firing since it is unable to identify start and end rows properly.
Comment