Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Merge branch 'worktree-agent-ad531323a21f4c975' | 1 | -- The order the log wrote events in. Ids are made when an event is |
| 2 | -- published, on whichever Worker published it, and events reach the log | |
| 3 | -- through a queue, so an event can be written after one with a later id. | |
| 4 | -- Following the log with an `after` cursor reads by this instead: what is | |
| 5 | -- written later always has a higher number, so a follower never skips one. | |
| 6 | -- Each insert takes the highest so far plus one; the log has one writer | |
| 7 | -- at a time. Events written before this have none and are not followed. | |
| 8 | ALTER TABLE events ADD COLUMN seq INTEGER; | |
| 9 | CREATE INDEX IF NOT EXISTS events_seq ON events (seq); | |
| 10 | CREATE INDEX IF NOT EXISTS events_repo_seq ON events (repo_id, seq); |
This file's history is long; its oldest lines are credited to the oldest commit read.