home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

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

issue 1

  • Support table names ending with .json or .csv · 4 ✖

author_association 1

  • OWNER 4
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
394037368 https://github.com/simonw/datasette/issues/303#issuecomment-394037368 https://api.github.com/repos/simonw/datasette/issues/303 MDEyOklzc3VlQ29tbWVudDM5NDAzNzM2OA== simonw 9599 2018-06-01T23:50:17Z 2018-06-01T23:50:35Z OWNER

Solution for he above: support an optional ?_format=json/csv parameter on the regular table view.

Then if you have tables with the above colliding names you can use /db/blah.json?_format=json

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Support table names ending with .json or .csv 328172521  
393600441 https://github.com/simonw/datasette/issues/303#issuecomment-393600441 https://api.github.com/repos/simonw/datasette/issues/303 MDEyOklzc3VlQ29tbWVudDM5MzYwMDQ0MQ== simonw 9599 2018-05-31T16:56:25Z 2018-05-31T16:57:41Z OWNER

Here's a nasty challenge: what happens if a database has the following two tables:

  • blah
  • blah.json

What would the URL be for the JSON endpoint for the blah table?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Support table names ending with .json or .csv 328172521  
393599840 https://github.com/simonw/datasette/issues/303#issuecomment-393599840 https://api.github.com/repos/simonw/datasette/issues/303 MDEyOklzc3VlQ29tbWVudDM5MzU5OTg0MA== simonw 9599 2018-05-31T16:54:22Z 2018-05-31T16:54:32Z OWNER

The interesting thing about this is that it requires URL routing to become aware of the names of all of the available tables.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Support table names ending with .json or .csv 328172521  
393557406 https://github.com/simonw/datasette/issues/303#issuecomment-393557406 https://api.github.com/repos/simonw/datasette/issues/303 MDEyOklzc3VlQ29tbWVudDM5MzU1NzQwNg== simonw 9599 2018-05-31T14:54:03Z 2018-05-31T14:54:03Z OWNER

Our test fixtures currently have a table with a name ending in .csv:

https://github.com/simonw/datasette/blob/d69ebce53385b7c6fafb85fdab3b136dbf3f332c/tests/fixtures.py#L234-L237

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Support table names ending with .json or .csv 328172521  

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 22.037ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows