issue_comments

Table actions

2 rows where issue = 508190730 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

  • Extremely simple migration system · 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
543222239 https://github.com/dogsheep/twitter-to-sqlite/issues/23#issuecomment-543222239 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/23 MDEyOklzc3VlQ29tbWVudDU0MzIyMjIzOQ== simonw 9599 2019-10-17T15:12:33Z 2019-10-17T15:12:33Z MEMBER

Migrations will run only if you open a database that previously existed (as opposed to opening a brand new empty database).

This means that the first time you run a command against a fresh database, migrations will not run and the migrations table will not be created. The second time you run any command against that database the migrations will execute and populate the migrations table.

This also means that each migration needs to be able to sanity check the database to see if it should run or not. If it should NOT run, it will do nothing but still be marked as having executed by adding to the migrations table.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Extremely simple migration system 508190730  
543217890 https://github.com/dogsheep/twitter-to-sqlite/issues/23#issuecomment-543217890 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/23 MDEyOklzc3VlQ29tbWVudDU0MzIxNzg5MA== simonw 9599 2019-10-17T15:03:10Z 2019-10-17T15:03:10Z MEMBER

Thinking about this further: the concept of migrations may end up being in direct conflict with the sqlite-utils concept of creating tables on demand the first time they are used - and of creating table schemas automatically to fit the shape of the JSON that is being inserted into them.

I'm going to forge ahead anyway and build this because I think it will be an interesting exploration, but it's very likely this turns out to be a bad idea in the long run!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Extremely simple migration system 508190730  

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