issue_comments

Table actions

1 row where author_association = "OWNER", issue = 1163369515 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 · 1 ✖

issue 1

  • query result page is using 400mb of browser memory 40x size of html page and 400x size of csv data · 1 ✖

author_association 1

  • OWNER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1062445113 https://github.com/simonw/datasette/issues/1655#issuecomment-1062445113 https://api.github.com/repos/simonw/datasette/issues/1655 IC_kwDOBm6k_c4_U6A5 simonw 9599 2022-03-09T01:01:24Z 2022-03-09T01:01:24Z OWNER

https://labordata.bunkum.us/-/settings shows max_returned_rows had been increased to 5,000 for that instance - the default of 1,000 would help a bit here.

Any thoughts on how Datasette could handle this kind of thing better?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 query result page is using 400mb of browser memory 40x size of html page and 400x size of csv data 1163369515  

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