issue_comments

Table actions

3 rows where issue = 317714268

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ html_url issue_url node_id user created_at updated_at author_association body reactions issue performed_via_github_app
384362028 https://github.com/simonw/datasette/issues/238#issuecomment-384362028 https://api.github.com/repos/simonw/datasette/issues/238 MDEyOklzc3VlQ29tbWVudDM4NDM2MjAyOA== simonw 9599 2018-04-25T17:07:11Z 2018-04-25T17:07:11Z OWNER On further thought: this is actually only an issue for immutable deployments to platforms like Zeit Now and Heroku. As such, adding it to `datasette serve` feels clumsy. Maybe `datasette publish` should instead gain the ability to optionally install an extra mechanism that periodically pulls a fresh copy of `metadata.json` from a URL. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} External metadata.json 317714268  
412291437 https://github.com/simonw/datasette/issues/238#issuecomment-412291437 https://api.github.com/repos/simonw/datasette/issues/238 MDEyOklzc3VlQ29tbWVudDQxMjI5MTQzNw== simonw 9599 2018-08-11T17:55:26Z 2018-08-11T18:02:48Z OWNER On further thought, I'd much rather implement this using some kind of metadata plugin hook - see #357 {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} External metadata.json 317714268  
504882244 https://github.com/simonw/datasette/issues/238#issuecomment-504882244 https://api.github.com/repos/simonw/datasette/issues/238 MDEyOklzc3VlQ29tbWVudDUwNDg4MjI0NA== simonw 9599 2019-06-24T06:52:45Z 2019-06-24T06:52:45Z OWNER I'm not going to do this - there are plenty of smarter ways of achieving a similar goal. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} External metadata.json 317714268  

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