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

fix: Fix Site Cache Layout Efficiency - MEED-8351 - Meeds-io/meeds#2883 #1052

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

boubaker
Copy link
Member

@boubaker boubaker commented Feb 5, 2025

Prior to this change, when requesting the Sites by their technical ids, the database is requested each time. This change will ensure to use the same cache for Site objects, either it has been retrieved by Id or by its Pretty SiteKey.

Resolves Meeds-io/meeds#2883

Prior to this change, when requesting the Sites by their technical ids, the database is requested each time. This change will ensure to use the same cache for Site objects, either it has been retrieved by id or by its Pretty SiteKey.
@boubaker boubaker enabled auto-merge (squash) February 5, 2025 09:11
@boubaker boubaker merged commit f10ab0f into develop Feb 5, 2025
5 checks passed
@boubaker boubaker deleted the meed-8351 branch February 5, 2025 09:27
exo-swf pushed a commit that referenced this pull request Feb 5, 2025
… (#1052)

Prior to this change, when requesting the Sites by their technical ids,
the database is requested each time. This change will ensure to use the
**same** cache for Site **objects**, either it has been retrieved by
`Id` or by its Pretty `SiteKey`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Site Layout Cache is missed while object is cached
2 participants