commits

Table actions

2 rows where author = 45057 and "author_date" is on date 2018-04-15 sorted by author_date descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: author_date (date), committer_date (date)

repo 1

author 1

  • russss · 2 ✖
sha message author_date ▲ committer_date raw_author raw_committer repo author committer
4586aa506a054d07e674cde8143a3008e6bc5d78 Don't duplicate simple primary keys in the link column When there's a simple (single-column) primary key, it looks weird to duplicate it in the link column. This change removes the second PK column and treats the link column as if it were the PK column from a header/sorting perspective. 2018-04-15T21:49:01Z 2018-04-18T01:13:02Z Russ Garrett cd9d55c7c0a7cc0ee69155676fd5e9fc6e1b884b Simon Willison 2946d096d0cdefdc017559e6b57e87658736e843 datasette 107914493 russss 45057 simonw 9599
b231d4243d748facf1897e7756c2b578bb448edc Correct escaping for HTML display of row links 2018-04-15T21:48:30Z 2018-04-18T01:13:02Z Russ Garrett cd9d55c7c0a7cc0ee69155676fd5e9fc6e1b884b Simon Willison 2946d096d0cdefdc017559e6b57e87658736e843 datasette 107914493 russss 45057 simonw 9599

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [commits] (
   [sha] TEXT PRIMARY KEY,
   [message] TEXT,
   [author_date] TEXT,
   [committer_date] TEXT,
   [raw_author] TEXT REFERENCES [raw_authors]([id]),
   [raw_committer] TEXT REFERENCES [raw_authors]([id]),
   [repo] INTEGER REFERENCES [repos]([id]),
   [author] INTEGER REFERENCES [users]([id]),
   [committer] INTEGER REFERENCES [users]([id])
);
CREATE INDEX [idx_commits_committer]
                ON [commits] ([committer]);
CREATE INDEX [idx_commits_author]
                ON [commits] ([author]);
CREATE INDEX [idx_commits_repo]
                ON [commits] ([repo]);
CREATE INDEX [idx_commits_raw_committer]
                ON [commits] ([raw_committer]);
CREATE INDEX [idx_commits_raw_author]
                ON [commits] ([raw_author]);