jonross / jonross/kugl

Actually cache in SQLite, not JSON

Open
#12 0 comments 0 reactions 0 assignees View on GitHub
idea
Dominant language
Python
Stars
7
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Parsing the saved `.json` files every time is slow.
Use SQLite itself as the cache.

Probably a bad idea because if you change table definitions, SQLite will be out of date.
We would need a checksum of each table config to confirm nothing changed.

So really we need both a SQLite db and the cache files

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.