This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 217
SQLCache Set should allow a null timeout #209
Comments
The Redis and DistributedMemory cache implementations allows this, I wonder why the SQL one doesn't. @kichalla? |
@iscifoni Thanks for reporting this. This behavior is not ideal. For now you could probably create a new extension on |
Tratcher
changed the title
SQLCache set default value on DistributedCacheEntryOptions
SQLCache Set should allow a null timeout
Jun 28, 2016
I am thinking that SQL Server cache should have a default sliding expiration for a cache entry, let's say 20 mins, if none specified by a user. These default timeout options would be exposed by @iscifoni any thoughts on this? |
kichalla
added a commit
that referenced
this issue
Jul 18, 2016
kichalla
added a commit
that referenced
this issue
Jul 18, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have implemented sql cache:
but when I execute the code, I receive the error "Either absolute or sliding expiration needs to be provided.".
This because at line 33 of Microsoft.Extensions.Caching.Abstractions/DistributedCacheExtensions.cs the DistributedCacheEntryOptions parameter is a new value, with no setting for AbsoluteExpirationRelativeToNow or SlidingExpiration property.
If i use
All works fine.
Need to modify Microsoft.Extensions.Caching.Abstractions/DistributedCacheExtensions.cs to pass default value forAbsoluteExpirationRelativeToNow or SlidingExpiration ??
The text was updated successfully, but these errors were encountered: