Skip to content

fix(AccountService): Invalidate cache after account creation/change/deletion#12803

Merged
ChristophWurst merged 1 commit intomainfrom
fix/invalidate-cache
Apr 24, 2026
Merged

fix(AccountService): Invalidate cache after account creation/change/deletion#12803
ChristophWurst merged 1 commit intomainfrom
fix/invalidate-cache

Conversation

@DerDreschner
Copy link
Copy Markdown
Contributor

While working on #12777, I found out that the cache isn't being invalidated after any change. This may cause some issues, although those will be very rare as the lifecycle of the AccountService class is limited to each request. For performance reasons, it may be worth to move the cache to memcache, which then will survive the lifecycle of the AccountService class.

AI-assisted: Claude Sonnet 4.6

…eletion

Signed-off-by: David Dreschner <david.dreschner@nextcloud.com>
Copy link
Copy Markdown
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense!

@ChristophWurst
Copy link
Copy Markdown
Member

/backport to stable5.7

@ChristophWurst ChristophWurst merged commit 797eab9 into main Apr 24, 2026
42 checks passed
@ChristophWurst ChristophWurst deleted the fix/invalidate-cache branch April 24, 2026 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants