issue_comments
2 rows where issue = 684118950
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 |
---|---|---|---|---|---|---|---|---|---|---|---|
678732667 | https://github.com/simonw/sqlite-utils/issues/138#issuecomment-678732667 | https://api.github.com/repos/simonw/sqlite-utils/issues/138 | MDEyOklzc3VlQ29tbWVudDY3ODczMjY2Nw== | simonw 9599 | 2020-08-23T05:46:10Z | 2020-08-23T05:46:10Z | OWNER | Actually the `TEXT` column thing wasn't a `sqlite-utils` issue, it was unique to how `shapefile-to-spatialite` was creating the table when using the SpatiaLite extension. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | extracts= doesn't configure foreign keys 684118950 | |
698626768 | https://github.com/simonw/sqlite-utils/issues/138#issuecomment-698626768 | https://api.github.com/repos/simonw/sqlite-utils/issues/138 | MDEyOklzc3VlQ29tbWVudDY5ODYyNjc2OA== | simonw 9599 | 2020-09-24T22:46:56Z | 2020-09-24T22:46:56Z | OWNER | Yeah this works fine, added a new confirmatory test. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | extracts= doesn't configure foreign keys 684118950 |
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]);