-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
Autodelete expired items #709
Comments
Hello, You just can't... Since you don't know who's are the expired items except by grabing 'em all (which is unimaginable). Cheers, |
You can simply auto delete expired items, your backend just needs to support it. @Geolim4 you build it in yourself, check the Couchbase plugin, that one supports it as Couchbase supports it. |
No, it repeat: I won't implement a feature not supported by 100% of the supported backends.... |
Why is it already in then ? |
It's not...
Re-read the docs, especially the API 😁
…On Thu, Nov 21, 2019, 8:01 PM Yamakasi ***@***.***> wrote:
No, it repeat: I won't implement a feature not supported by 100% of the
supported backends....
Why is it already in then ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#709?email_source=notifications&email_token=AAKFGZ33IJD7IBXGFTMPYTLQU3LHRA5CNFSM4I3RXO22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE3JOBA#issuecomment-557225732>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKFGZYAPJNBZZP2OPAD7EDQU3LHRANCNFSM4I3RXO2Q>
.
|
If you set expired with ->expiresAfter(INT) for an item the backend does the rest if it knows how to handle expired documents/items. No re-read for the docs, just know how your backend works and implement the right one. |
What don't you understand in "some blackend" does not implement "queryable
expired items".
If I decided not to implement it it's because that kind of feature is not
implementable in some backends (file, memcache, etc...)
So, end of discussion, this is not a receivable request at the moment since
not standardized.
…On Thu, Nov 21, 2019, 8:09 PM Yamakasi ***@***.***> wrote:
It's not... Re-read the docs, especially the API 😁
[…]
If you set expired with ->expiresAfter(INT) for an item the backend does
the rest if it knows how to handle expired documents/items.
No re-read for the docs, just know how your backend works and implement
the right one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#709?email_source=notifications&email_token=AAKFGZ6JERL7EVV34UB32BTQU3MGPA5CNFSM4I3RXO22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE3KHAA#issuecomment-557228928>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKFGZ5ERE4EYPMPM353CILQU3MGPANCNFSM4I3RXO2Q>
.
|
It would be good to have an ability to autodelete expired items.
The text was updated successfully, but these errors were encountered: