issue_comments

Table actions

2 rows where issue = 521323012 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

issue 1

  • Support Python 3.8, stop supporting Python 3.5 · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
609393513 https://github.com/simonw/datasette/pull/627#issuecomment-609393513 https://api.github.com/repos/simonw/datasette/issues/627 MDEyOklzc3VlQ29tbWVudDYwOTM5MzUxMw== stonebig 4312421 2020-04-05T10:23:57Z 2020-04-05T10:23:57Z NONE

is there any specific reason to stick to Jinja2~=2.10.3 when there is Jinja-2.11.1 ?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Support Python 3.8, stop supporting Python 3.5 521323012  
552737357 https://github.com/simonw/datasette/pull/627#issuecomment-552737357 https://api.github.com/repos/simonw/datasette/issues/627 MDEyOklzc3VlQ29tbWVudDU1MjczNzM1Nw== willingc 2680980 2019-11-12T05:13:46Z 2019-11-12T05:13:46Z NONE

Thanks @simonw. I appreciate your work on this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Support Python 3.8, stop supporting Python 3.5 521323012  

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