issue_comments
5 rows where author_association = "OWNER" and "updated_at" is on date 2020-09-08
This data as json, CSV (advanced)
Suggested facets: issue_url
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
689163158 | https://github.com/simonw/sqlite-utils/issues/155#issuecomment-689163158 | https://api.github.com/repos/simonw/sqlite-utils/issues/155 | MDEyOklzc3VlQ29tbWVudDY4OTE2MzE1OA== | simonw 9599 | 2020-09-08T22:10:27Z | 2020-09-08T22:10:27Z | OWNER | For the command version: sqlite-utils rebuild-fts mydb.db This will rebuild all detected FTS tables. You can also specify one or more explicit tables: sqlite-utils rebuild-fts mydb.db dogs | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | rebuild-fts command and table.rebuild_fts() method 696045581 | |
689165985 | https://github.com/simonw/sqlite-utils/issues/153#issuecomment-689165985 | https://api.github.com/repos/simonw/sqlite-utils/issues/153 | MDEyOklzc3VlQ29tbWVudDY4OTE2NTk4NQ== | simonw 9599 | 2020-09-08T22:18:52Z | 2020-09-08T22:18:52Z | OWNER | I've reverted this change again, because it turns out using the `rebuild` FTS mechanism is a better way of repairing this issue - see #155. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | table.optimize() should delete junk rows from *_fts_docsize 695377804 | |
689166404 | https://github.com/simonw/sqlite-utils/issues/155#issuecomment-689166404 | https://api.github.com/repos/simonw/sqlite-utils/issues/155 | MDEyOklzc3VlQ29tbWVudDY4OTE2NjQwNA== | simonw 9599 | 2020-09-08T22:20:03Z | 2020-09-08T22:20:03Z | OWNER | I'm going to update `sqlite-utils optimize` to also take an optional list of tables, for consistency. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | rebuild-fts command and table.rebuild_fts() method 696045581 | |
689185393 | https://github.com/simonw/sqlite-utils/pull/146#issuecomment-689185393 | https://api.github.com/repos/simonw/sqlite-utils/issues/146 | MDEyOklzc3VlQ29tbWVudDY4OTE4NTM5Mw== | simonw 9599 | 2020-09-08T23:17:42Z | 2020-09-08T23:17:42Z | OWNER | That seems like a reasonable approach to me, especially since this is going to be a pretty rare edge-case. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Handle case where subsequent records (after first batch) include extra columns 688668680 | |
689186423 | https://github.com/simonw/sqlite-utils/issues/145#issuecomment-689186423 | https://api.github.com/repos/simonw/sqlite-utils/issues/145 | MDEyOklzc3VlQ29tbWVudDY4OTE4NjQyMw== | simonw 9599 | 2020-09-08T23:21:23Z | 2020-09-08T23:21:23Z | OWNER | Fixed in PR #146. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Bug when first record contains fewer columns than subsequent records 688659182 |
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]);
updated_at (date) 1 ✖