issue_comments

Table actions

1 row where author_association = "OWNER", issue = 620969465 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

  • Allow to specify a URL fragment for canned queries · 1 ✖

author_association 1

  • OWNER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
632398475 https://github.com/simonw/datasette/issues/767#issuecomment-632398475 https://api.github.com/repos/simonw/datasette/issues/767 MDEyOklzc3VlQ29tbWVudDYzMjM5ODQ3NQ== simonw 9599 2020-05-21T23:36:00Z 2020-05-21T23:36:00Z OWNER

Interesting. So this would take effect exclusively on pages that link to the queries, which I think just means this page: https://latest.datasette.io/fixtures

How about this for the design: there's a new optional key in the metadata configuration for a query called "fragment" - used like this:

json { "databases": { "fixtures": { "queries": { "neighborhood_search": { "sql": "\nselect neighborhood, facet_cities.name, state\nfrom facetable\n join facet_cities\n on facetable.city_id = facet_cities.id\nwhere neighborhood like '%' || :text || '%'\norder by neighborhood;\n", "title": "Search neighborhoods", "description_html": "<b>Demonstrating</b> simple like search", "name": "neighborhood_search", "fragment": "sql-format" } } } } } Because of the "fragment": "sql-format" bit there the link to that query from https://latest.datasette.io/fixtures would be to https://latest.datasette.io/fixtures/neighborhood_search#sql-format.

Does that cover what you need here? Have I missed anything?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Allow to specify a URL fragment for canned queries 620969465  

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