geopython / geopython/GeoHealthCheck

Use caching features in SQL Alchemy

Open
#399 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
92
Forks
75
PR merge metrics
No merged PRs in 30d

Description

Follow up on issue #395, which is now closed.

[Here](https://github.com/geopython/GeoHealthCheck/issues/395#issuecomment-910291945) Just mentioned the following:
> From what I learned: the latest versions of SQLAlchemy (v2 I think and up) having caching-features internally. Our `SQLAlchemy==1.3.8` and `Flask-SQLAlchemy==2.4.0` are really old but upgrades failed earlier, at least will take time.
> In general I would prefer a solution via SQLAlchemy.

It is a good idea to check if this works well, so my fix in #394 can be reimplemented.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.