issue_comments

Table actions

3 rows where author_association = "OWNER", issue = 695377804 and user = 9599 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

  • table.optimize() should delete junk rows from *_fts_docsize · 3 ✖

author_association 1

  • OWNER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
689165985 https://github.com/simonw/sqlite-utils/issues/153#issuecomment-689165985 https://api.github.com/repos/simonw/sqlite-utils/issues/153 MDEyOklzc3VlQ29tbWVudDY4OTE2NTk4NQ== simonw 9599 2020-09-08T22:18:52Z 2020-09-08T22:18:52Z OWNER

I've reverted this change again, because it turns out using the rebuild FTS mechanism is a better way of repairing this issue - see #155.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.optimize() should delete junk rows from *_fts_docsize 695377804  
688511161 https://github.com/simonw/sqlite-utils/issues/153#issuecomment-688511161 https://api.github.com/repos/simonw/sqlite-utils/issues/153 MDEyOklzc3VlQ29tbWVudDY4ODUxMTE2MQ== simonw 9599 2020-09-07T21:07:20Z 2020-09-07T21:07:29Z OWNER

FTS4 uses a different column name here: https://datasette-sqlite-fts4.datasette.io/24ways-fts4/articles_fts_docsize

CREATE TABLE 'articles_fts_docsize'(docid INTEGER PRIMARY KEY, size BLOB);

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.optimize() should delete junk rows from *_fts_docsize 695377804  
688506015 https://github.com/simonw/sqlite-utils/issues/153#issuecomment-688506015 https://api.github.com/repos/simonw/sqlite-utils/issues/153 MDEyOklzc3VlQ29tbWVudDY4ODUwNjAxNQ== simonw 9599 2020-09-07T20:46:58Z 2020-09-07T20:46:58Z OWNER

Writing a test for this will be a tiny bit tricky. I think I'll use a test that replicates the bug in #149.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 table.optimize() should delete junk rows from *_fts_docsize 695377804  

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