issue_comments

Table actions

2 rows where "created_at" is on date 2020-03-20, issue = 585266763 and "updated_at" is on date 2020-03-20 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

issue 1

  • IndexError running user-timeline command · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
601871579 https://github.com/dogsheep/twitter-to-sqlite/issues/34#issuecomment-601871579 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/34 MDEyOklzc3VlQ29tbWVudDYwMTg3MTU3OQ== simonw 9599 2020-03-20T19:20:52Z 2020-03-20T19:20:52Z MEMBER

Cause was the redefining of how upsert() works in sqlite-utils 2.x.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 IndexError running user-timeline command 585266763  
601861908 https://github.com/dogsheep/twitter-to-sqlite/issues/34#issuecomment-601861908 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/34 MDEyOklzc3VlQ29tbWVudDYwMTg2MTkwOA== simonw 9599 2020-03-20T18:56:44Z 2020-03-20T18:56:44Z MEMBER

Could this be a bug in sqlite-utils? This table has a primary key, so why is it running a query on rowid = ??

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 IndexError running user-timeline command 585266763  

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