issue_comments: 527682713

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions issue performed_via_github_app
https://github.com/dogsheep/twitter-to-sqlite/issues/4#issuecomment-527682713 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/4 527682713 MDEyOklzc3VlQ29tbWVudDUyNzY4MjcxMw== 9599 2019-09-03T23:48:57Z 2019-09-03T23:48:57Z MEMBER

One interesting challenge here is that the JSON format for tweets in the archive is subtly different from the JSON format currently returned by the API.

If we want to keep the tweets in the same database table (which feels like the right thing to me) we'll need to handle this.

One thing we can do is have a column for from_archive which is set to 1 for tweets that were recovered from the archive.

We can also ensure that tweets from the API always over-write the version that came from the archive (using .upsert()) while tweets from the archive use .insert(..., ignore=True) to avoid over-writing a better version that came from the API.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 488835586