issue_comments
6 rows where "updated_at" is on date 2018-05-14 sorted by user
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date)
id | html_url | issue_url | node_id | user ▼ | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
388684356 | https://github.com/simonw/datasette/issues/256#issuecomment-388684356 | https://api.github.com/repos/simonw/datasette/issues/256 | MDEyOklzc3VlQ29tbWVudDM4ODY4NDM1Ng== | simonw 9599 | 2018-05-14T03:05:37Z | 2018-05-14T03:05:37Z | OWNER | I just landed pull request #257 - I haven't refactored the tests, I may do that later if it looks worthwhile. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Break up app.py into separate view modules 322551723 | |
388686463 | https://github.com/simonw/datasette/issues/255#issuecomment-388686463 | https://api.github.com/repos/simonw/datasette/issues/255 | MDEyOklzc3VlQ29tbWVudDM4ODY4NjQ2Mw== | simonw 9599 | 2018-05-14T03:23:44Z | 2018-05-14T03:25:22Z | OWNER | It would be neat if there was a mechanism for calculating aggregates per facet - e.g. calculating the sum() of specific columns against each facet result on https://datasette-facets-demo.now.sh/fivethirtyeight-2628db9/nba-elo%2Fnbaallelo?_facet=lg_id&_facet=fran_id&lg_id=ABA&_facet=team_id | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Facets 322477187 | |
388784063 | https://github.com/simonw/datasette/issues/255#issuecomment-388784063 | https://api.github.com/repos/simonw/datasette/issues/255 | MDEyOklzc3VlQ29tbWVudDM4ODc4NDA2Mw== | simonw 9599 | 2018-05-14T11:25:00Z | 2018-05-14T11:25:15Z | OWNER | Can I get facets working across many2many relationships? This would be fiendishly useful, but the querystring and `metadata.json` syntax is non-obvious. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Facets 322477187 | |
388784787 | https://github.com/simonw/datasette/issues/255#issuecomment-388784787 | https://api.github.com/repos/simonw/datasette/issues/255 | MDEyOklzc3VlQ29tbWVudDM4ODc4NDc4Nw== | simonw 9599 | 2018-05-14T11:28:05Z | 2018-05-14T11:28:05Z | OWNER | To decide which facets to suggest: for each column, is the unique value count less than the number of rows matching the current query or is it less than 20 (if we are showing more than 20 rows)? Maybe only do this if there are less than ten non-float columns. Or always try for foreign keys and booleans, then if there are none of those try indexed text and integer fields, then finally try non-indexed text and integer fields but only if there are less than ten. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Facets 322477187 | |
388797919 | https://github.com/simonw/datasette/issues/259#issuecomment-388797919 | https://api.github.com/repos/simonw/datasette/issues/259 | MDEyOklzc3VlQ29tbWVudDM4ODc5NzkxOQ== | simonw 9599 | 2018-05-14T12:23:11Z | 2018-05-14T12:23:11Z | OWNER | For M2M to work we will need a mechanism for applying IN queries to the table view, so you can select multiple M2M filters. Maybe this would work: ?_m2m_category=123&_m2m_category=865 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | inspect() should detect many-to-many relationships 322787470 | |
388987044 | https://github.com/simonw/datasette/issues/251#issuecomment-388987044 | https://api.github.com/repos/simonw/datasette/issues/251 | MDEyOklzc3VlQ29tbWVudDM4ODk4NzA0NA== | simonw 9599 | 2018-05-14T22:47:55Z | 2018-05-14T22:47:55Z | OWNER | This work is now happening in the facets branch. Closing this in favor of #255. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Explore "distinct values for column" in inspect() 320592643 |
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]);
updated_at (date) 1 ✖