issue_comments

Table actions

6 rows where issue = 488833975 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • simonw · 6 ✖

issue 1

  • Command for running a search and saving tweets for that search · 6 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
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  
549096321 https://github.com/dogsheep/twitter-to-sqlite/issues/3#issuecomment-549096321 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/3 MDEyOklzc3VlQ29tbWVudDU0OTA5NjMyMQ== simonw 9599 2019-11-03T01:27:55Z 2019-11-03T01:28:17Z MEMBER

It would be neat if this could support --since, with that argument automatically finding the maximum tweet ID from a previous search that used the same exact arguments (using the search_runs table).

 
{
    "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  
543290744 https://github.com/dogsheep/twitter-to-sqlite/issues/3#issuecomment-543290744 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/3 MDEyOklzc3VlQ29tbWVudDU0MzI5MDc0NA== simonw 9599 2019-10-17T17:57:14Z 2019-10-17T17:57:14Z MEMBER

I have a working command now. I'm going to ship it early because it could do with some other people trying it out.

 
{
    "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  
543273540 https://github.com/dogsheep/twitter-to-sqlite/issues/3#issuecomment-543273540 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/3 MDEyOklzc3VlQ29tbWVudDU0MzI3MzU0MA== simonw 9599 2019-10-17T17:12:51Z 2019-10-17T17:12:51Z MEMBER

Just importing tweets here isn't enough - how are we supposed to know which tweets were imported by which search?

So I think the right thing to do here is to also create a search_runs table, which records each individual run of this tool (with a timestamp and the search terms used). Then have a search_runs_tweets m2m table which shows which Tweets were found by that search.

 
{
    "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  
541493242 https://github.com/dogsheep/twitter-to-sqlite/issues/3#issuecomment-541493242 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/3 MDEyOklzc3VlQ29tbWVudDU0MTQ5MzI0Mg== simonw 9599 2019-10-14T03:35:36Z 2019-10-14T03:35:36Z 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  

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