![]() |
Sergey Kornilov admin 7/6/2007 |
Good point - we need to think how to handle records count in this case. |
C
|
ccuser author 7/6/2007 |
The only way I can think of to work around this was if there were a way to edit the sql query on page load so you can filter the results by a where statement. Then since the pagination function is called after $strsql is executed the row count would be correct. |
![]() |
Sergey Kornilov admin 7/6/2007 |
We'll have this option in the next update (in two weeks). |
C
|
ccuser author 7/16/2007 |
Curious to know if this timeline is still valid? We'll have this option in the next update (in two weeks). |
A
|
alang 9/6/2007 |
I am also having problems with this issue (using build 297). I have set the list page to return potentially hundreds of records at 20/page. Based on a parameter passed in the call to display the page I want to be able to select a subset of records to display on the list page (potentially around 5% of the total returned by the basic SQL statement. I have access to the SQL string in the "BeforeQueryList" event but cannot use that because the information used to "screen" the records has come from another database. I then select which records to display by returning true/false in the "BeforeProcessRowList" event.
|
A
|
alang 9/9/2007 |
Sorry - please ignore #2 (PHP error) in my last post - that was being caused by another problem. |
![]() |
Sergey Kornilov admin 9/10/2007 |
I'm afraid I miss the question. |
A
|
alang 9/10/2007 |
Sorry - As an example, I have a list page that would normally return 400 records. If I have the records per page set to 20, I get 20 records on each of 20 pages as expected. If I then add code to the "Before Record Processed" event such that it returns TRUE for 1 in every 10 records and FALSE for the others, I end up with 20 pages with only 2 records displayed on each page. I would prefer/expect to see 2 pages with 20 records on each page. |