issue_comments

Table actions

1 row where issue = 440134714, "updated_at" is on date 2019-06-04 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • simonw · 1 ✖

issue 1

  • Define mechanism for plugins to return structured data · 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
498838841 https://github.com/simonw/datasette/issues/446#issuecomment-498838841 https://api.github.com/repos/simonw/datasette/issues/446 MDEyOklzc3VlQ29tbWVudDQ5ODgzODg0MQ== simonw 9599 2019-06-04T20:51:37Z 2019-06-04T20:51:37Z OWNER

So the Python 3.7 way to do this would be dataclasses, but I still want to support 3.5.

This excellent essay has made me think attrs might be the way to go: https://www.revsys.com/tidbits/dataclasses-and-attrs-when-and-why/

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Define mechanism for plugins to return structured data 440134714  

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