Skip to content

Time-travel for your MySQL. DB Trail remembers every row change: searchable, reversible, yours. The wrong UPDATE becomes a two-minute fix.

active 2026-06-092026-09-01 (UTC)

Complete coverage26,778 / 26,778 hourly files (100%) · 2 absent upstream2023-08-152026-09-03 (UTC)
Events
644
Pushes
307
Pull requests
21
Issues
69
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 85 days from 2026-06-09 to 2026-09-01. Pushes: 307 total, peak 21 in a day. Pull requests: 21 total, peak 3 in a day. Issues: 69 total, peak 57 in a day. Comments: 6 total, peak 2 in a day. Stars: 0 total, peak 0 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
nethalo399305205
dependabot[bot]3210
154321001

Recent activity

Latest issues, pull requests and releases

  • Pull request#1413nethalo2026-08-21 21:12
  • Pull request#1409nethalo2026-08-21 15:48
  • Pull request#1264nethalo2026-08-07 20:22
  • Issue#1165nethalo2026-08-07 19:05
    Epic: state materialization — self-refreshing baselines and a queryable state tier in Parquet
  • Issue comment#1262nethalo2026-08-07 17:41
    verify: PG-native live-source consistency checksum
  • Issue comment#1262154322026-08-07 17:03
    verify: PG-native live-source consistency checksum
  • Issue#1177nethalo2026-08-07 16:52
    console: server-side SQL panel over the archive — security requirements (parked)
  • Pull request#1260dependabot[bot]2026-08-07 14:30
  • Issue#1198nethalo2026-07-31 20:48
    reconstruct/shim: PG-shaped snapshot on the MySQL path still gets the misleading 'PK type unsupported' message (sibling of #1009)
  • Pull request#1053nethalo2026-07-19 00:28
  • Pull request#1043nethalo2026-07-17 17:08
  • Pull request#869nethalo2026-07-05 20:33
  • Issue#857nethalo2026-07-05 01:53
    docs: dump-and-baseline.md — anchor described as "where deltas start" but code uses a 1s timestamp; document the dump-host TZ=UTC requirement
  • Issue#857nethalo2026-07-05 01:53
    docs: dump-and-baseline.md — anchor described as "where deltas start" but code uses a 1s timestamp; document the dump-host TZ=UTC requirement
  • Issue#857nethalo2026-07-05 01:53
    docs: dump-and-baseline.md — anchor described as "where deltas start" but code uses a 1s timestamp; document the dump-host TZ=UTC requirement
  • Issue#839nethalo2026-07-05 01:52
    query: FetchSnapshot applies LIMIT without ORDER BY — non-deterministic subset of baseline rows
  • Issue#839nethalo2026-07-05 01:52
    query: FetchSnapshot applies LIMIT without ORDER BY — non-deterministic subset of baseline rows
  • Issue#839nethalo2026-07-05 01:52
    query: FetchSnapshot applies LIMIT without ORDER BY — non-deterministic subset of baseline rows
  • Issue#834nethalo2026-07-05 01:52
    cascade: FK graph used is the latest snapshot, not the one in effect at delete time
  • Issue#834nethalo2026-07-05 01:52
    cascade: FK graph used is the latest snapshot, not the one in effect at delete time
  • Issue#828nethalo2026-07-05 01:52
    pg: publications with a ROW FILTER (PG15+) pass all validation and silently capture only a subset of changes
  • Issue#828nethalo2026-07-05 01:52
    pg: publications with a ROW FILTER (PG15+) pass all validation and silently capture only a subset of changes
  • Issue#828nethalo2026-07-05 01:52
    pg: publications with a ROW FILTER (PG15+) pass all validation and silently capture only a subset of changes
  • Issue#827nethalo2026-07-05 01:52
    pg: TRUNCATE leaves NO trace in the index — only a warn in the daemon log
  • Issue#827nethalo2026-07-05 01:52
    pg: TRUNCATE leaves NO trace in the index — only a warn in the daemon log

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