Skip to content
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.

Implement a caching mechanism #39

Open
agateblue opened this issue Jul 19, 2016 · 1 comment
Open

Implement a caching mechanism #39

agateblue opened this issue Jul 19, 2016 · 1 comment

Comments

@agateblue
Copy link
Owner

It would be great to implement caching on various to minimize IO operations.
@agateblue
Copy link
Owner Author

My first implementation was kind of dummy, the hooks for getting / settings a cache value are not at the proper place. Instead of caching the final result (model instances, and so on, we should cache the underlying backend (SQL, http...) response.

@agateblue agateblue reopened this Jul 20, 2016
agateblue pushed a commit that referenced this issue Jul 20, 2016
Merge tag '0.4' into develop
570d3d4 
0.4 (2016-7-20)
---------------

This release introduces the django contrib module to enable filtering with lifter's python backend
on a django queryset, effectively reducing number of queries sent to the database.

Work is also in progress regarding caching (see #39) but this is not over yet.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@agateblue