FoundKeyGang/FoundKey
FoundKeyGang/FoundKey
7
19
Fork 22
Code Issues 37 Pull requests 4 Releases Activity

expire old notifications #292

New issue
Closed
opened 2022-12-18 01:15:45 +00:00 by Johann150 · 0 comments
Johann150 commented 2022-12-18 01:15:45 +00:00
Owner
Copy link

Currently notifications are stored in the database indefinitely. I think at some point it does not make sense to store notifications. We might want to expire them after a certain amount of time has passed or something similar.

For example we could expire all notifications that have been read and are older than 1 year.

Currently notifications are stored in the database indefinitely. I think at some point it does not make sense to store notifications. We might want to expire them after a certain amount of time has passed or something similar. For example we could expire all notifications that have been read and are older than 1 year.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
refactor-deliver-actor
markdown
move-autoblock
feature/requests
context
indicator-circle-v2
v13.0.0-preview6
v13.0.0-preview5.1
v13.0.0-preview5
v13.0.0-preview4
v13.0.0-preview3
v13.0.0-preview2
v13.0.0-preview1
Labels
Clear labels   
feature

task that proposes new feature(s)

  
fix

task to fix behavioral problems in the FoundKey codebase

  
upkeep

task that should make FoundKey smaller and more maintainable

No labels
feature
fix
upkeep
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: FoundKeyGang/FoundKey#292
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?