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

Is a cache.lock_dir needed when using ext:database ? #55

Open
neilferreira opened this issue Dec 16, 2013 · 2 comments
Open

Is a cache.lock_dir needed when using ext:database ? #55

neilferreira opened this issue Dec 16, 2013 · 2 comments

Comments

@neilferreira
Copy link

After having a read on http://turbogears.org/2.1/docs/main/Caching.html#configuring-beaker I just need to confirm this.

Do I need a cache.lock_dir directory when using ext:database? The docs make no mention of it unlike the file/memory cache, but I can see the lock_dir being referenced inside the code for sqlalchemy's handler.

@EndenDragon
Copy link

It apparently does not, as far as I know.

@amol-
Copy link
Collaborator

amol- commented Apr 29, 2017

Like any other cache the file lock is used to prevent dogpile effect. If it's not provided tempfile.gettempdir() will be used.

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

3 participants