commits
1 row where "author_date" is on date 2017-11-13 and message = "Limit on max rows returned, controlled by --max_returned_rows option If someone executes 'select * from table' against a table with a million rows in it, we could run into problems: just serializing that much data as JSON is likely to lock up the server. Solution: we now have a hard limit on the maximum number of rows that can be returned by a query. If that limit is exceeded, the server will return a `"truncated": true` field in the JSON. This limit can be optionally controlled by the new `--max_returned_rows` option. Setting that option to 0 disables the limit entirely. Closes #69"
This data as json, CSV (advanced)
Suggested facets: author_date (date), committer_date (date)
sha ▼ | author_date | committer_date | raw_author | raw_committer | repo | author | committer |
---|---|---|---|---|---|---|---|
8252e71da461c425e625e1c3e4ee0bd92ea4cbf0 | 2017-11-13T19:33:01Z | 2017-11-13T19:33:01Z | Simon Willison 2946d096d0cdefdc017559e6b57e87658736e843 | Simon Willison 2946d096d0cdefdc017559e6b57e87658736e843 | datasette 107914493 | 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]);