issue_comments

Table actions

1 row where issue = 626211658 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

  • Ability to configure keyset pagination for views and queries · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
702493047 https://github.com/simonw/datasette/issues/778#issuecomment-702493047 https://api.github.com/repos/simonw/datasette/issues/778 MDEyOklzc3VlQ29tbWVudDcwMjQ5MzA0Nw== simonw 9599 2020-10-02T02:26:25Z 2020-10-02T02:26:25Z OWNER

I think this could work for arbitrary SQL queries too. Those would need querystring configuration that specifies which sorted column(s) should be used for the "next" cursor.

One example: I'd like to be able to offer a paginated list of counts of values in a table - e.g. this query:

https://fivethirtyeight.datasettes.com/fivethirtyeight?sql=select+replies%2C+count%28%29+from+%5Btwitter-ratio%2Fsenators%5D+group+by+replies+order+by+count%28%29+desc%3B

That could even become a query that gets linked to from the column actions menu.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to configure keyset pagination for views and queries 626211658  

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