Slow pagination with GCE v3

Hello @bgeneto ,

This is a feature not a bug

In short, there is a delay of 1 second so the user will decide which page they would like to have. I am testing the grid into 1,000,000 rows and every query request is heavy so I am trying to have as less requests as possible.

So in short:

• first page or last page → Since the user know that they would like to go in the last page then it is happening instantly
• next or previous page → How many times you want to go into page 3 and instead of typing the number “3” you just press 2 times the next button. I do that often

At the above example the request started 1 second later and the user has been informed with the extra loading icon. Also we have skipped the request for the page “2” which is unnecessary. Keep in mind that even if I cancel the request, the backend request (e.g. SQL query) is still running causing performance and memory issues.

• The solution to have it instantly is to press the page and then press “Enter”. This will send the page to be triggered instantly.

There is lot of optimization in the background and a hard-work checking every little scenario even for edge case scenarios like this. I hope it make more sense now

Regards
Johnny

Hello @bgeneto ,

No this is not an easy change unfortunately. Maybe this can be done in your case with a bit of JavaScript on your side

Try this:

window.addEventListener('gcrud.datagrid.page-change', () => {
 document.querySelector(".grocery-crud .fa-sync-alt").click();
});

and make sure that you have the “publish_events” configuration to true. For more about how to use JavaScript events you can check JavaScript Events | Grocery CRUD - A PHP CRUD Generator Library

Regards
Johnny

Hello @bgeneto ,

After playing around with the paging (to solve the filtering issue) I’ve decided that I will remove completely the delay . As I said to the previous post, I am preparing a new major version (no breaking changes don’t worry!) which will be the 3.1 so please be a little patient.

Regards
Johnny

Hello @bgeneto ,

I am glad to inform you that at the latest version 3.1.0 the paging is instant.

Regards
Johnny

Hello @bgeneto ,

As I’ve also wrote to the configuration value it self:

Include JavaScript files in the main output and don’t return them at ‘js_files’ variable.
This is useful for quicker installations/demos, but it is recommended to set this to false
and have all of your JavaScript files at the bottom of your page before the tag.
Please consider that when JavaScript files are included directly in the output, you lose the ability
to control when and where these files are loaded.

So in short if this is true you can remove the js_files from your view. It is one step less for newcomers basically

In the future, I am trying to have installations with less steps. I will also probably create a blog post for version 3.1 to also describe this configuration in more details.