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

Enh/add caching #527

Merged
merged 7 commits into from
Jul 11, 2023
Merged

Enh/add caching #527

merged 7 commits into from
Jul 11, 2023

Conversation

jdkent
Copy link
Member

@jdkent jdkent commented Jul 11, 2023

  • I've considered some of the weird relationships between tables: annotations and studyset_studies to make sure the caches are invalidated when there are changes to other tables
  • I've considered when authorization is passed with the headers (like when looking at the studies endpoint when you have studies that you own that would show up during a search)
  • I have considered the nesting of objects so when you update a coordinate, you should invalidate the cache of analyses, studies, etc.
  • there are likely weird scenarios afoot, maybe if a point is deleted and an analysis is viewed without nesting, the id of the point may still show up?

@jdkent
Copy link
Member Author

jdkent commented Jul 11, 2023

be ready for weird errors!

@jdkent jdkent merged commit 6df5203 into master Jul 11, 2023
15 checks passed
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.

None yet

1 participant