Jordan Cook

@glensc ^ See this issue. It is a tradeoff, and I can't predict exactly what updates might break requests-cache in the future, but I think there are [some good arguments...

I could imagine this being potentially useful if you already have a relational db instance and want to keep all your data in one place, or if you wanted to...

Several releases later, I think this library is in a better position to add support for SQLAlchemy without introducing a huge amount of complexity. And if a full ORM model...

This is an idea for the future, but not planning to implement it right now.

Interesting idea. Do you happen to have any cases where the key you want to ignore is more than 1 level deep (like `data.key_1.key_2`)? If not, that would make things...

That would be great! I don't think the `filter_sort_*` functions need to change, but `normalize_json_body` and everything up the call chain from there will need to change. To get you...

This is an idea for the future, but not planning to implement it right now.

The duplicate read issue is now fixed in #438

> Wondering if this is a known and expected behavior of the newer package version. Yes, unfortunately the cache keys change for almost every non-patch release. New features and other...

Some changes are now in `main` to make this easier. Now you can run this after updating to a new requests-cache version, or after changing any settings related to [request...