issue_comments

Table actions

2 rows where issue = 518739697, "updated_at" is on date 2019-11-09 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • simonw · 2 ✖

issue 1

  • `followers` fails because `transform_user` is called twice · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
552133468 https://github.com/dogsheep/twitter-to-sqlite/issues/30#issuecomment-552133468 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/30 MDEyOklzc3VlQ29tbWVudDU1MjEzMzQ2OA== simonw 9599 2019-11-09T20:15:27Z 2019-11-09T20:15:27Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `followers` fails because `transform_user` is called twice 518739697  
552131798 https://github.com/dogsheep/twitter-to-sqlite/issues/30#issuecomment-552131798 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/30 MDEyOklzc3VlQ29tbWVudDU1MjEzMTc5OA== simonw 9599 2019-11-09T19:54:45Z 2019-11-09T19:54:45Z MEMBER

Good catch - not sure how that bug crept in. Removing line 116 looks like the right fix to me.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `followers` fails because `transform_user` is called twice 518739697  

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