Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit and Columns with huge tables #369

Open
portapipe opened this issue Aug 31, 2016 · 5 comments
Open

Limit and Columns with huge tables #369

portapipe opened this issue Aug 31, 2016 · 5 comments

Comments

@portapipe
Copy link
Contributor

portapipe commented Aug 31, 2016

Hi, it's me again 😄
I have a customer with a very old and untouchable website. One of his db table has over 16k heavy rows that I can't limit with GC (the limit seems to not work and not limit at all) plus the columns property doesn't filter the data but just show that column and that is quite heavy for the page.

I should divide that rows every 5k rows but the limit ignore his job.

Maybe I use something wrong?
Thanks :)

@adrianogoncalves
Copy link

Try to change the theme to datatables.

@portapipe
Copy link
Contributor Author

portapipe commented Aug 31, 2016

Hi. I have the premium bootstrap theme installed. Tested with other theme, same problem.
And I think $select = "{$this->table_name}.*"; is not so good for performance

@mckaygerhard
Copy link

is 2021 and this problem still happened..

@scoumbourdis
Copy link
Owner

scoumbourdis commented Sep 4, 2021

Hello @mckaygerhard, I agree with you but please keep in mind that this has been resolved on Grocery CRUD Enterprise. This change that was needed unfortunately required a complete refactoring of the code in order to have better performance and this was literally impossible at the old code base.

@mckaygerhard
Copy link

It is understandable that the old code is not possible, but I see that so little in the "new code" since when you say "enterprice" you make it seem like what better to buy than to solve ..

I have a partial solution to the problem in the old code modifying the model, thus giving a real support to the "where" since the boostrap is not really taking into account @scoumbourdis

in fact the problem is pretty simple.. the "where" is not honour, by example i made a form that forces the where dinamically, that is not take if i refresh the page.. so a ajax resend of that solved the problem!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants