issue_comments

Table actions

1 row where issue = 705190723

✎ 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
695839557 https://github.com/simonw/sqlite-utils/issues/160#issuecomment-695839557 https://api.github.com/repos/simonw/sqlite-utils/issues/160 MDEyOklzc3VlQ29tbWVudDY5NTgzOTU1Nw== simonw 9599 2020-09-20T21:37:03Z 2020-09-20T21:37:03Z OWNER Should this support `ignore=True` as well? I'm tempted to skip that - I think `replace=True` is more useful because it implies "ignore if the options are already the same, but replace if they are different". {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} table.enable_fts(..., replace=True) 705190723  

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