issue_comments

Table actions

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

  • Add --cors argument to serve · 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
344000982 https://github.com/simonw/datasette/issues/75#issuecomment-344000982 https://api.github.com/repos/simonw/datasette/issues/75 MDEyOklzc3VlQ29tbWVudDM0NDAwMDk4Mg== simonw 9599 2017-11-13T17:50:27Z 2017-11-13T17:50:27Z OWNER

This is necessary because one of the fun things to do with this tool is run it locally, e.g.:

 datasette ~/Library/Application\ Support/Google/Chrome/Default/History -p 8003

BUT... if we enable CORS by default, an evil site could try sniffing for localhost:8003 and attempt to steal data.

So we'll enable the CORS headers only if --cors is provided to the command, and then use that command in the default Dockerfile.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add --cors argument to serve 273509159  

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