issue_comments
5 rows where issue = 447408527
This data as json, CSV (advanced)
Suggested facets: user, author_association, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 495032818 | https://github.com/simonw/datasette/issues/483#issuecomment-495032818 | https://api.github.com/repos/simonw/datasette/issues/483 | MDEyOklzc3VlQ29tbWVudDQ5NTAzMjgxOA== | simonw 9599 | 2019-05-23T01:28:06Z | 2019-05-23T01:28:06Z | OWNER | Here's a UI concept: <img width="418" alt="fixtures__facetable__15_rows" src="https://user-images.githubusercontent.com/9599/58219350-551be500-7cbf-11e9-84ae-3b0386ae2063.png"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Option to facet by date using month or year 447408527 | |
| 495032933 | https://github.com/simonw/datasette/issues/483#issuecomment-495032933 | https://api.github.com/repos/simonw/datasette/issues/483 | MDEyOklzc3VlQ29tbWVudDQ5NTAzMjkzMw== | simonw 9599 | 2019-05-23T01:28:45Z | 2019-05-23T01:28:45Z | OWNER | Would this be useful for other facets? How many facet types are likely to have a small number of options that could be linked to in this way? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Option to facet by date using month or year 447408527 | |
| 495034774 | https://github.com/simonw/datasette/issues/483#issuecomment-495034774 | https://api.github.com/repos/simonw/datasette/issues/483 | MDEyOklzc3VlQ29tbWVudDQ5NTAzNDc3NA== | jcmkk3 45919695 | 2019-05-23T01:38:32Z | 2019-05-23T01:43:04Z | NONE | I think that location information is one of the other common pieces of hierarchical data. At least one that is general enough that extra dimensions could be auto-generated. Also, I think this is an awesome project. Thank you for creating this. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Option to facet by date using month or year 447408527 | |
| 495080390 | https://github.com/simonw/datasette/issues/483#issuecomment-495080390 | https://api.github.com/repos/simonw/datasette/issues/483 | MDEyOklzc3VlQ29tbWVudDQ5NTA4MDM5MA== | simonw 9599 | 2019-05-23T06:06:53Z | 2019-05-23T06:06:53Z | OWNER | Yes there's definitely something exciting to be done with location facets. The easiest one would be a radius-distance-from-a-point facet (5km, 10km etc). A more sophisticated thing might be possible on top of GeoJSON and SpatiaLite - that's probably something I would put in a plugin rather than shipping in Datasette itself. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Option to facet by date using month or year 447408527 | |
| 495080591 | https://github.com/simonw/datasette/issues/483#issuecomment-495080591 | https://api.github.com/repos/simonw/datasette/issues/483 | MDEyOklzc3VlQ29tbWVudDQ5NTA4MDU5MQ== | simonw 9599 | 2019-05-23T06:07:53Z | 2019-05-23T06:09:05Z | OWNER | As far as URL design goes... I'm going to stick with `?_facet_date=` for this and use the not-yet-fully-baked JSON alternative syntax. Probably something like this: ?_facet_date={"column":"created","interval":"month"} Where interval can be day (the default), month or year. And maybe week? Not sure about that. Still not sure what/if I should do about exposing these options in the UI. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Option to facet by date using month or year 447408527 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);