dogsheep / dogsheep/github-to-sqlite

Does subsequent calls fetch all data or only new/updated data?

Offen
#83 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
474
Forks
50
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

I was hoping/expecting that subsequent calls to github-to-sqlite would only fetch and update new or updated data. Ie, first call for populating the entire database might be heavy, with thousands of API calls, while subsequent calls most of the time will be only dozens of api calls.

However, I just did this test, for a repo with 845 issues:

$ time github-to-sqlite issues github.db simonw/llm

real 1m50.375s
user 0m10.361s
sys 0m6.230s

$ time github-to-sqlite issues github.db simonw/llm

real 1m49.710s
user 0m10.277s
sys 0m5.981s

It seems that it fetches from scratch, every time. Can you confirm?

If yes, please consider this a feature request for a smarter update, or secondarily a request for improving the docs to make this behavior clear :)

Thanks for providing this tool, sincerely, Thomas

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.