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.

Sign up for GitHub

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

Jump to bottom

capabilities should be cached within geoDB client #82

Open
thomasstorm opened this issue Aug 17, 2023 · 1 comment · May be fixed by #83
Open

capabilities should be cached within geoDB client #82

thomasstorm opened this issue Aug 17, 2023 · 1 comment · May be fixed by #83
Assignees
@thomasstorm
Labels
enhancement New feature or request

Comments

@thomasstorm
Copy link
Contributor

Fetching the capabilities of the database can be a quite costly operation (> 3secs) when often repeated. By caching the property, subsequent calls to self.capabilities within the client can be done within a milisecond.
@thomasstorm thomasstorm added the enhancement New feature or request label Aug 17, 2023
@thomasstorm thomasstorm self-assigned this Aug 17, 2023
thomasstorm added a commit that referenced this issue Aug 17, 2023
@thomasstorm
fixed #82
cc4fb88
thomasstorm added a commit that referenced this issue Aug 17, 2023
@thomasstorm
finished fix for #82
3a953e9
@thomasstorm thomasstorm linked a pull request Aug 17, 2023 that will close this issue
Open
6 tasks
@thomasstorm thomasstorm mentioned this issue Feb 9, 2024
Merged
6 tasks
@thomasstorm thomasstorm reopened this Feb 20, 2024
@thomasstorm
Copy link
Contributor Author

Errorneously closed due to a typo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thomasstorm thomasstorm

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Cache capabilities xcube-dev/xcube-geodb
1 participant
@thomasstorm