issue_comments

Table actions

4 rows where issue = 341123355 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

issue 1

  • Requesting support for query description · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
405138460 https://github.com/simonw/datasette/issues/342#issuecomment-405138460 https://api.github.com/repos/simonw/datasette/issues/342 MDEyOklzc3VlQ29tbWVudDQwNTEzODQ2MA== simonw 9599 2018-07-16T02:42:32Z 2018-07-16T02:42:32Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Requesting support for query description 341123355  
404954672 https://github.com/simonw/datasette/issues/342#issuecomment-404954672 https://api.github.com/repos/simonw/datasette/issues/342 MDEyOklzc3VlQ29tbWVudDQwNDk1NDY3Mg== simonw 9599 2018-07-13T21:09:01Z 2018-07-13T21:09:01Z OWNER

So it would look like this: { "databases": { "timezones": { "license": "ODbL", "license_url": "http://opendatacommons.org/licenses/odbl/", "queries": { "by_point": { "title": "Timezones by point", "description": "Find the timezone for a latitude/longitude point", "sql": "select tzid\nfrom\n timezones\nwhere\n within(GeomFromText('POINT(' || :longitude || ' ' || :latitude || ')'), timezones.Geometry)\n and rowid in (\n SELECT pkid FROM idx_timezones_Geometry\n where xmin < :longitude\n and xmax > :longitude\n and ymin < :latitude\n and ymax > :latitude\n )" } } } } }

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Requesting support for query description 341123355  
404954202 https://github.com/simonw/datasette/issues/342#issuecomment-404954202 https://api.github.com/repos/simonw/datasette/issues/342 MDEyOklzc3VlQ29tbWVudDQwNDk1NDIwMg== simonw 9599 2018-07-13T21:06:53Z 2018-07-13T21:07:13Z OWNER

https://timezones-api.now.sh/-/metadata currently shows this: { "databases": { "timezones": { "license": "ODbL", "license_url": "http://opendatacommons.org/licenses/odbl/", "queries": { "by_point": "select tzid\nfrom\n timezones\nwhere\n within(GeomFromText(\u0027POINT(\u0027 || :longitude || \u0027 \u0027 || :latitude || \u0027)\u0027), timezones.Geometry)\n and rowid in (\n SELECT pkid FROM idx_timezones_Geometry\n where xmin \u003c :longitude\n and xmax \u003e :longitude\n and ymin \u003c :latitude\n and ymax \u003e :latitude\n )" }, "source": "timezone-boundary-builder", "source_url": "https://github.com/evansiroky/timezone-boundary-builder", "tables": { "timezones": { "license": "ODbL", "license_url": "http://opendatacommons.org/licenses/odbl/", "sortable_columns": [ "tzid" ], "source": "timezone-boundary-builder", "source_url": "https://github.com/evansiroky/timezone-boundary-builder" } } } }, "license": "ODbL", "license_url": "http://opendatacommons.org/licenses/odbl/", "source": "timezone-boundary-builder", "source_url": "https://github.com/evansiroky/timezone-boundary-builder", "title": "OpenStreetMap Time Zone Boundaries" }

We could support the value part of the "queries" array optionally being a dictionary with the same set of metadata fields supported for a table, plus a new "sql" key to hold the SQL for the query.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Requesting support for query description 341123355  
404953877 https://github.com/simonw/datasette/issues/342#issuecomment-404953877 https://api.github.com/repos/simonw/datasette/issues/342 MDEyOklzc3VlQ29tbWVudDQwNDk1Mzg3Nw== simonw 9599 2018-07-13T21:05:12Z 2018-07-13T21:05:12Z OWNER

That's a good idea. We already do this for tables - e.g. on https://fivethirtyeight.datasettes.com/fivethirtyeight-ac35616/most-common-name%2Fsurnames - so having it as an option for canned queries definitely makes sense.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Requesting support for query description 341123355  

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