home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where "created_at" is on date 2020-04-26 and issue = 534492501 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 3

issue 1

  • Mechanism for adding arbitrary pages like /about · 3 ✖

author_association 1

  • OWNER 3
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
619612675 https://github.com/simonw/datasette/issues/648#issuecomment-619612675 https://api.github.com/repos/simonw/datasette/issues/648 MDEyOklzc3VlQ29tbWVudDYxOTYxMjY3NQ== simonw 9599 2020-04-26T19:35:09Z 2020-04-26T19:35:09Z OWNER

https://www.niche-museums.com/about now uses this mechanism. It used to be an empty about.db database but you can see from https://www.niche-museums.com/-/databases that it's now using the new mechanism.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Mechanism for adding arbitrary pages like /about 534492501  
619604720 https://github.com/simonw/datasette/issues/648#issuecomment-619604720 https://api.github.com/repos/simonw/datasette/issues/648 MDEyOklzc3VlQ29tbWVudDYxOTYwNDcyMA== simonw 9599 2020-04-26T18:50:30Z 2020-04-26T18:50:30Z OWNER

Documentation: https://datasette.readthedocs.io/en/latest/custom_templates.html#custom-pages

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Mechanism for adding arbitrary pages like /about 534492501  
619591380 https://github.com/simonw/datasette/issues/648#issuecomment-619591380 https://api.github.com/repos/simonw/datasette/issues/648 MDEyOklzc3VlQ29tbWVudDYxOTU5MTM4MA== simonw 9599 2020-04-26T17:33:04Z 2020-04-26T17:33:04Z OWNER

Stretch goal: it would be neat if these pages could return custom HTTP headers (eg content-type) and maybe even status codes (eg for redirects) somehow.

I think I could do that with a custom template function - if that function is called during the render then we follow those instructions instead of returning the rendered HTML.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Mechanism for adding arbitrary pages like /about 534492501  

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]);
Powered by Datasette · Queries took 18.68ms · About: github-to-sqlite