Skip to content

Use triggers to track when rows in a SQLite table were updated or deleted

active 2025-04-272026-06-16 (UTC)

Partial coverage11,660 / 12,835 hourly files (91%) · 2 absent upstream · 1,171 failed, retryable2025-02-222026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
52
Pushes
16
Pull requests
1
Issues
6
Stars
8
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 416 days from 2025-04-27 to 2026-06-16. Pushes: 16 total, peak 13 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 6 total, peak 3 in a day. Comments: 15 total, peak 10 in a day. Stars: 8 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
simonw3816115

Recent activity

Latest issues, pull requests and releases

  • Issue#24simonw2026-02-15 15:09
    I deleted records should get a new added_ms
  • Issue#24simonw2026-02-15 14:58
    I deleted records should get a new added_ms
  • Issue#6simonw2026-02-15 06:33
    Utility function for disabling chronicle
  • Issue comment#20simonw2026-02-15 06:21
    Get INSERT OR REPLACE INTO working after all
  • Issue comment#20simonw2026-02-15 05:06
    Get INSERT OR REPLACE INTO working after all
  • Pull request#19simonw2026-01-06 05:01
  • Issue comment#17simonw2025-05-09 23:41
    upgrade_chronicle() function for upgrading from previous schema designs
  • Issue comment#17simonw2025-05-09 23:37
    upgrade_chronicle() function for upgrading from previous schema designs
  • Issue#17simonw2025-05-09 23:33
    upgrade_chronicle() function for upgrading from previous schema designs
  • Issue#16simonw2025-05-09 23:16
    Add SQL schema to README, powered by cog
  • Issue#16simonw2025-05-09 23:16
    Add SQL schema to README, powered by cog
  • Issue comment#7simonw2025-05-09 04:04
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 04:44
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 04:39
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 04:37
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 04:35
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 04:02
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 04:01
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 03:59
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 03:55
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 03:50
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO
  • Issue comment#7simonw2025-04-27 03:46
    added_ms and updated_ms columns are not reliable in face of operations like INSERT OR REPLACE INTO

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 8 stars here means stars gained during the window, not the repo's star count.