issue_comments

Table actions

2 rows where issue = 974067156

✎ View and edit SQL

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
901440207 https://github.com/simonw/sqlite-utils/issues/318#issuecomment-901440207 https://api.github.com/repos/simonw/sqlite-utils/issues/318 IC_kwDOCGYnMM41uuLP simonw 9599 2021-08-18T21:24:28Z 2021-08-18T21:24:49Z OWNER Something like this then: sqlite-utils file.db "select * from t" --csv --gz > t.csv.gz Maybe add a `-o t.csv.gz` option too so you don't have to use a `>`. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Research: handle gzipped CSV directly 974067156  
901440752 https://github.com/simonw/sqlite-utils/issues/318#issuecomment-901440752 https://api.github.com/repos/simonw/sqlite-utils/issues/318 IC_kwDOCGYnMM41uuTw simonw 9599 2021-08-18T21:25:30Z 2021-08-18T21:25:30Z OWNER Some questions: - Should this support compression formats other than gzip? - Should `memory` learn to auto-detect gzipped data? {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Research: handle gzipped CSV directly 974067156  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);