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.

Sign up for GitHub

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

Jump to bottom

CACHE: Lazy-Results still get added to cache which might fill memory #14

Open
Osiris-Team opened this issue May 13, 2023 · 1 comment
Open

CACHE: Lazy-Results still get added to cache which might fill memory #14

Osiris-Team opened this issue May 13, 2023 · 1 comment

Comments

@Osiris-Team
Copy link
Owner

The whole point of getLazy() is to be able to work with extremely large tables by not getting all the results directly, but lazily step-wise in smaller portions. However when cache is enabled the last requests stay in the memory which defeats the whole purpose of the getLazy() method.
@Osiris-Team
Copy link
Owner Author

This could be fixed by adding a general size limit to the cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Osiris-Team