issue_comments: 607011421

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/40#issuecomment-607011421 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/40 607011421 MDEyOklzc3VlQ29tbWVudDYwNzAxMTQyMQ== 9599 2020-04-01T03:47:37Z 2020-04-01T03:55:08Z MEMBER

Actually a single table with a type integer ID referencing a count_history_types table would better match the way I implemented the since_ids table:

https://github.com/dogsheep/twitter-to-sqlite/blob/4b6c8d8c1cc6fefdb566ec8506157133f47c569a/twitter_to_sqlite/utils.py#L331-L341

In which case the compound primary key would be type, user, datetime

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