issue_comments

Table actions

1 row where author_association = "NONE", issue = 1077560091 and user = 3153638 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

  • Profpatsch · 1 ✖

issue 1

  • Data Pull fails for "Essential" level access to the Twitter API (for Documentation) · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1297201971 https://github.com/dogsheep/twitter-to-sqlite/issues/61#issuecomment-1297201971 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/61 IC_kwDODEm0Qs5NUbsz Profpatsch 3153638 2022-10-31T14:47:58Z 2022-10-31T14:47:58Z NONE

There’s also a limit of 3200 tweets. I wonder if that can be circumvented somehow.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Data Pull fails for "Essential" level access to the Twitter API (for Documentation) 1077560091  

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