issue_comments
2 rows where issue = 695376054
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
688500294 | https://github.com/simonw/sqlite-utils/issues/152#issuecomment-688500294 | https://api.github.com/repos/simonw/sqlite-utils/issues/152 | MDEyOklzc3VlQ29tbWVudDY4ODUwMDI5NA== | simonw 9599 | 2020-09-07T20:27:07Z | 2020-09-07T20:27:07Z | OWNER | I'm going to make this an argument to the `Database()` class constructor which defaults to `True`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Turn on recursive_triggers by default 695376054 | |
688500704 | https://github.com/simonw/sqlite-utils/issues/152#issuecomment-688500704 | https://api.github.com/repos/simonw/sqlite-utils/issues/152 | MDEyOklzc3VlQ29tbWVudDY4ODUwMDcwNA== | simonw 9599 | 2020-09-07T20:28:45Z | 2020-09-07T21:17:48Z | OWNER | The principle reason to turn these on - at least so far - is that without it weird things happen where FTS tables (in particular `*_fts_docsize`) grow without limit over time, because calls to `INSERT OR REPLACE` against the parent table cause additional rows to be inserted into `*_fts_docsize` even if the row was replaced rather than being inserted. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Turn on recursive_triggers by default 695376054 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);