issue_comments

Table actions

5 rows where "created_at" is on date 2020-03-20, issue = 585282212 and "updated_at" is on date 2020-03-20 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

issue 1

  • twitter-to-sqlite user-timeline [screen_names] --sql / --attach · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
601892338 https://github.com/dogsheep/twitter-to-sqlite/issues/35#issuecomment-601892338 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/35 MDEyOklzc3VlQ29tbWVudDYwMTg5MjMzOA== simonw 9599 2020-03-20T20:17:00Z 2020-03-20T20:17:00Z MEMBER

Released as 0.18.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 twitter-to-sqlite user-timeline [screen_names] --sql / --attach 585282212  
601890795 https://github.com/dogsheep/twitter-to-sqlite/issues/35#issuecomment-601890795 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/35 MDEyOklzc3VlQ29tbWVudDYwMTg5MDc5NQ== simonw 9599 2020-03-20T20:13:08Z 2020-03-20T20:13:08Z MEMBER

Needs documentation.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 twitter-to-sqlite user-timeline [screen_names] --sql / --attach 585282212  
601875405 https://github.com/dogsheep/twitter-to-sqlite/issues/35#issuecomment-601875405 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/35 MDEyOklzc3VlQ29tbWVudDYwMTg3NTQwNQ== simonw 9599 2020-03-20T19:30:09Z 2020-03-20T19:32:33Z MEMBER

I'm going to redesign the command a little. Right now it defaults to fetching the authenticated user's timeline and allows --screen_name to be used to fetch for one other user instead.

I think the design of users-lookup is much better. I'm going to copy that:

twitter-to-sqlite user-timeline users.db simonw cleopaws twitter-to-sqlite user-timeline users.db 12497 3166449535 --ids It will also accept --since and --sql and --alter and --since_id.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 twitter-to-sqlite user-timeline [screen_names] --sql / --attach 585282212  
601876051 https://github.com/dogsheep/twitter-to-sqlite/issues/35#issuecomment-601876051 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/35 MDEyOklzc3VlQ29tbWVudDYwMTg3NjA1MQ== simonw 9599 2020-03-20T19:31:43Z 2020-03-20T19:31:43Z MEMBER

I'm going to keep --screen_name working for backwards compatibility. Using hidden=True on it should hide it from the help output.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 twitter-to-sqlite user-timeline [screen_names] --sql / --attach 585282212  
601875524 https://github.com/dogsheep/twitter-to-sqlite/issues/35#issuecomment-601875524 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/35 MDEyOklzc3VlQ29tbWVudDYwMTg3NTUyNA== simonw 9599 2020-03-20T19:30:27Z 2020-03-20T19:30:27Z MEMBER

I can give it a snazzier progress bar to, as requested by #10.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 twitter-to-sqlite user-timeline [screen_names] --sql / --attach 585282212  

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