issue_comments

Table actions

2 rows where issue = 508578780

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

id ▼ html_url issue_url node_id user created_at updated_at author_association body reactions issue performed_via_github_app
543265058 https://github.com/dogsheep/twitter-to-sqlite/issues/25#issuecomment-543265058 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/25 MDEyOklzc3VlQ29tbWVudDU0MzI2NTA1OA== simonw 9599 2019-10-17T16:51:12Z 2019-10-17T16:51:12Z MEMBER This migration function only runs if there is a table called `tweets` and the migration has not run before. I think this can happen if the database has just been freshly created (by a command that fetches the user's user timeline for example) and is then run a SECOND time. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ensure migrations don't accidentally create foreign key twice 508578780  
543266947 https://github.com/dogsheep/twitter-to-sqlite/issues/25#issuecomment-543266947 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/25 MDEyOklzc3VlQ29tbWVudDU0MzI2Njk0Nw== simonw 9599 2019-10-17T16:56:06Z 2019-10-17T16:56:06Z MEMBER I wrote a test that proves that this is a problem. Should be an easy fix though. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ensure migrations don't accidentally create foreign key twice 508578780  

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