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

How does this handle values with no expiration? #3

Closed
nwp opened this issue Jul 30, 2012 · 1 comment
Closed

How does this handle values with no expiration? #3

nwp opened this issue Jul 30, 2012 · 1 comment
Labels

Comments

@nwp
Copy link
Contributor

nwp commented Jul 30, 2012

See https://github.com/mdx-dev/li3_mongodb_cache/blob/master/extensions/adapter/storage/cache/MongoDb.php#L152 where the criteria always includes expiration. What if you're not using TTL collections, and you set a cached value with no expiration (null). When you attempt to read that value, will that criteria eliminate the previous cached value due to the fact that null is not greater than now?

@bayleedev
Copy link
Contributor

TTL does not put an expire flag into the collection. Source

If no expire is set it'll use the config. Source. If the config is null, and the params are null it WILL be interpreted to 0 (zero) and not be able to be found.

Can this be closed?

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

No branches or pull requests

2 participants