issue_comments

Table actions

4 rows where "created_at" is on date 2019-09-03 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

user 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
527684202 https://github.com/dogsheep/twitter-to-sqlite/issues/5#issuecomment-527684202 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/5 MDEyOklzc3VlQ29tbWVudDUyNzY4NDIwMg== simonw 9599 2019-09-03T23:56:28Z 2019-09-03T23:56:28Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Write tests that simulate the Twitter API 488874815  
527682713 https://github.com/dogsheep/twitter-to-sqlite/issues/4#issuecomment-527682713 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/4 MDEyOklzc3VlQ29tbWVudDUyNzY4MjcxMw== simonw 9599 2019-09-03T23:48:57Z 2019-09-03T23:48:57Z MEMBER

One interesting challenge here is that the JSON format for tweets in the archive is subtly different from the JSON format currently returned by the API.

If we want to keep the tweets in the same database table (which feels like the right thing to me) we'll need to handle this.

One thing we can do is have a column for from_archive which is set to 1 for tweets that were recovered from the archive.

We can also ensure that tweets from the API always over-write the version that came from the archive (using .upsert()) while tweets from the archive use .insert(..., ignore=True) to avoid over-writing a better version that came from the API.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Command for importing data from a Twitter Export file 488835586  
527266798 https://github.com/simonw/sqlite-utils/pull/57#issuecomment-527266798 https://api.github.com/repos/simonw/sqlite-utils/issues/57 MDEyOklzc3VlQ29tbWVudDUyNzI2Njc5OA== simonw 9599 2019-09-03T01:03:59Z 2019-09-03T01:03:59Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add triggers while enabling FTS 487987958  
527266687 https://github.com/simonw/datasette/issues/560#issuecomment-527266687 https://api.github.com/repos/simonw/datasette/issues/560 MDEyOklzc3VlQ29tbWVudDUyNzI2NjY4Nw== simonw 9599 2019-09-03T01:03:02Z 2019-09-03T01:03:02Z OWNER

This is released in 0.29.3

Compare https://v0-29.datasette.io/fixtures (broken) with https://v0-29-3.datasette.io/fixtures (fixed)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 CodeMirror fails to load on database page 467790646  

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