home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 585353598 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

  • simonw 3

issue 1

  • Handle "User not found" error · 3 ✖

author_association 1

  • MEMBER 3
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
615510361 https://github.com/dogsheep/twitter-to-sqlite/issues/37#issuecomment-615510361 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/37 MDEyOklzc3VlQ29tbWVudDYxNTUxMDM2MQ== simonw 9599 2020-04-17T23:38:27Z 2020-04-17T23:38:27Z MEMBER

That's a bit tricky since I'd have to rewrite the internals of a bunch of other commands. For the moment I'll exit the script with an error but at least it will be a decent error!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Handle "User not found" error 585353598  
615509803 https://github.com/dogsheep/twitter-to-sqlite/issues/37#issuecomment-615509803 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/37 MDEyOklzc3VlQ29tbWVudDYxNTUwOTgwMw== simonw 9599 2020-04-17T23:36:40Z 2020-04-17T23:36:40Z MEMBER

I'm going to print a warning to stderr, skip and continue - because if you have 100 screen names and only one of them is invalid you should still execute for the other 99.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Handle "User not found" error 585353598  
615509578 https://github.com/dogsheep/twitter-to-sqlite/issues/37#issuecomment-615509578 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/37 MDEyOklzc3VlQ29tbWVudDYxNTUwOTU3OA== simonw 9599 2020-04-17T23:36:00Z 2020-04-17T23:36:00Z MEMBER

$ twitter-to-sqlite user-timeline doggo.db doggoenthuonetuh Traceback (most recent call last): ... File "/Users/simonw/Dropbox/Development/twitter-to-sqlite/twitter_to_sqlite/utils.py", line 272, in transform_user user["created_at"] = parser.parse(user["created_at"]) KeyError: 'created_at'

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Handle "User not found" error 585353598  

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]);
Powered by Datasette · Queries took 20.241ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows