-
Notifications
You must be signed in to change notification settings - Fork 21
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
Is it possible to cache application level settings? #19
Comments
This is not something that Setler does currently, but it would be a nice feature to have. |
I set this up on my application in the Settings class which was extending Setler. You could roll a lot of this into Setler itself fairly easily. Also, make sure that this is turned off during tests. I wasn't sure how to do per-request detection from a model so there is a very rigged up solution in the code instead.
|
Would be nice if the "thing id" = null's out there that are generally application level settings were somehow cacheable to avoid invoking a query every time the setting needed to be checked.
Starts to add up after a while in a high traffic app especially if there are multiple settings per page. Is there any way to do that currently? I didn't see it in the README.
The text was updated successfully, but these errors were encountered: