commits
1 row where author = 9599 and message = "table.add_foreign_key(column, other_table, other_column) New mechanism for adding foreign key constraints to an existing SQLite table. SQLite ALTER TABLE does not support this out-of-the-box, so I instead had to write some careful code that uses PRAGMA writable_schema = 1 to directly modify the sqlite_master table. Refs #2" sorted by author_date descending
This data as json, CSV (advanced)
Suggested facets: author_date (date), committer_date (date)
repo 1
sha | author_date ▲ | committer_date | raw_author | raw_committer | repo | author | committer |
---|---|---|---|---|---|---|---|
e1ca938aa1c84367fd9d4786b9709c56f3e6e778 | 2019-02-24T21:10:51Z | 2019-02-24T21:10:51Z | Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 | Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 | sqlite-utils 140912432 | simonw 9599 | simonw 9599 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);