issue_comments

Table actions

5 rows where author_association = "MEMBER" and "created_at" is on date 2019-11-04 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

author_association 1

  • MEMBER · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
549233778 https://github.com/dogsheep/github-to-sqlite/pull/8#issuecomment-549233778 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/8 MDEyOklzc3VlQ29tbWVudDU0OTIzMzc3OA== simonw 9599 2019-11-04T06:14:40Z 2019-11-04T06:14:40Z MEMBER

Spotted a tricky problem: running github-to-sqlite starred stargazers.db results in an incomplete simonw record. It creates a proper record for me thanks to this bit:

https://github.com/dogsheep/github-to-sqlite/blob/ea07274667a08c67907e8bfbbccb6f0fb95ce817/github_to_sqlite/cli.py#L120-L126

But then... when it gets to the datasette repository which I have starred it over-writes my full user record with one that's missing most of the details, thanks to this bit:

https://github.com/dogsheep/github-to-sqlite/blob/ea07274667a08c67907e8bfbbccb6f0fb95ce817/github_to_sqlite/utils.py#L117-L124

I need to find a way of NOT over-writing a good record with a thinner one.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 stargazers command, refs #4 516763727  
549230583 https://github.com/dogsheep/github-to-sqlite/pull/8#issuecomment-549230583 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/8 MDEyOklzc3VlQ29tbWVudDU0OTIzMDU4Mw== simonw 9599 2019-11-04T05:49:26Z 2019-11-04T05:49:26Z MEMBER

Adding the view from #10 would be useful here too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 stargazers command, refs #4 516763727  
549230337 https://github.com/dogsheep/github-to-sqlite/issues/10#issuecomment-549230337 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/10 MDEyOklzc3VlQ29tbWVudDU0OTIzMDMzNw== simonw 9599 2019-11-04T05:47:18Z 2019-11-04T05:47:18Z MEMBER

This definition isn't quite right - it's not pulling the identity of the user who starred the repo (users.login ends up being the owner login instead).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add this repos_starred view 516967682  
549228535 https://github.com/dogsheep/twitter-to-sqlite/issues/3#issuecomment-549228535 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/3 MDEyOklzc3VlQ29tbWVudDU0OTIyODUzNQ== simonw 9599 2019-11-04T05:31:55Z 2019-11-04T05:31:55Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Command for running a search and saving tweets for that search 488833975  
549226399 https://github.com/dogsheep/twitter-to-sqlite/issues/3#issuecomment-549226399 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/3 MDEyOklzc3VlQ29tbWVudDU0OTIyNjM5OQ== simonw 9599 2019-11-04T05:11:57Z 2019-11-04T05:11:57Z MEMBER

I'm going to add a hash column to search_runs to support that. It's going to be the sha1 hash of the key-ordered JSON of the search arguments used by that run. Then --since can look for an identical hash and use it to identify the highest last fetched tweet to use in since_id.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Command for running a search and saving tweets for that search 488833975  

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