issue_comments

Table actions

1 row where issue = 455996809

✎ 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
511259493 https://github.com/simonw/sqlite-utils/issues/28#issuecomment-511259493 https://api.github.com/repos/simonw/sqlite-utils/issues/28 MDEyOklzc3VlQ29tbWVudDUxMTI1OTQ5Mw== simonw 9599 2019-07-15T02:37:20Z 2019-07-15T02:37:20Z OWNER I've changed my mind on this one. I don't think the docs will read particularly well if they try to cover both of these things at once. I could set up links between the two, but actually trying to combine them feels like it will result in documentation that is less useful. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Rearrange the docs by area, not CLI vs Python 455996809  

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