Do you have any query condition to filter our the data?
The SQL is quite long with lots of conditions, but what happens is that first time into the page it only shows 50 records. If I just refresh the page then all 400 are shown. So it would appear to be something in the grid that is saying only return the first 50 rows but it does not realise there is more to come later when you step through to the following pages.
Looking at the apex debug output, it has appended the following to the query,
where ROWNUM <= :p$_max_rows
Where is p$_max_rows defined? Could it be this that is stopping it.
Any ideas on this?
1 person found this helpful
Info: I work with Jeremy
Seems that Apex has led us a little dance here.
There is a page item in the query for the IG containing a date in DD-MON-YYYY format.
On entry to the page - the page item is empty.
When we run the IG source SQL in the underlying schema - 0 rows are returned.
In the Apex page IG - we are having 50 rows returned - but when paginating past page 5 (10 rows per page) - no rows are returned
We currently have no explanation for the 50 rows being returned but it is consistent.
(yes - have cleared cache for all time and restarted browser and retested this situation)
Defaulting the page item in a pre-header process TO_CHAR(SYSDATE,'DD-MON-YYYY') has resolved the 50 rows issue