issue_comments
11 rows where "created_at" is on date 2018-05-27, issue = 326800219 and reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Mechanism for customizing the SQL used to select specific columns in the table view · 11 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
392343839 | https://github.com/simonw/datasette/issues/292#issuecomment-392343839 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM0MzgzOQ== | simonw 9599 | 2018-05-27T16:10:09Z | 2018-06-04T17:38:04Z | OWNER | The more efficient way of doing this kind of count would be to provide a mechanism which can also add extra fragments to a Or... how about a mechanism similar to Django's Related to that: since the per-query overhead in SQLite is tiny, could even define an extra query to be run once-per-row before returning results. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392350980 | https://github.com/simonw/datasette/issues/292#issuecomment-392350980 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM1MDk4MA== | simonw 9599 | 2018-05-27T17:56:30Z | 2018-05-27T17:56:50Z | OWNER | Should |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392350568 | https://github.com/simonw/datasette/issues/292#issuecomment-392350568 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM1MDU2OA== | simonw 9599 | 2018-05-27T17:48:45Z | 2018-05-27T17:54:41Z | OWNER | If any |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392350495 | https://github.com/simonw/datasette/issues/292#issuecomment-392350495 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM1MDQ5NQ== | simonw 9599 | 2018-05-27T17:47:31Z | 2018-05-27T17:47:31Z | OWNER | Querystring design:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392345062 | https://github.com/simonw/datasette/issues/292#issuecomment-392345062 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM0NTA2Mg== | simonw 9599 | 2018-05-27T16:26:53Z | 2018-05-27T16:26:53Z | OWNER | There needs to be a way to turn this off and return to Datasette default bahviour. Maybe a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392343690 | https://github.com/simonw/datasette/issues/292#issuecomment-392343690 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM0MzY5MA== | simonw 9599 | 2018-05-27T16:08:25Z | 2018-05-27T16:08:40Z | OWNER | Turns out it's actually possible to pull data from other tables using the mechanism in the prototype:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392342947 | https://github.com/simonw/datasette/issues/292#issuecomment-392342947 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM0Mjk0Nw== | simonw 9599 | 2018-05-27T16:01:43Z | 2018-05-27T16:01:43Z | OWNER | I'd still like to be able to over-ride this using querystring arguments. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392342269 | https://github.com/simonw/datasette/issues/292#issuecomment-392342269 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjM0MjI2OQ== | simonw 9599 | 2018-05-27T15:55:40Z | 2018-05-27T16:01:26Z | OWNER | Here's the metadata I tried against that first working prototype:
Run using this:
Usefully, the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392338130 | https://github.com/simonw/datasette/issues/292#issuecomment-392338130 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjMzODEzMA== | simonw 9599 | 2018-05-27T15:09:18Z | 2018-05-27T15:09:28Z | OWNER | Here's my first sketch at a metadata format for this:
Can you facet by things that are customized using If omitted, the If you want the row page to switch back to Datasette's default behaviour you can set |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392316701 | https://github.com/simonw/datasette/issues/292#issuecomment-392316701 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjMxNjcwMQ== | simonw 9599 | 2018-05-27T09:08:49Z | 2018-05-27T09:08:49Z | OWNER | I could certainly see people wanting different custom column selects for the row page compared to the table page. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 | |
392316673 | https://github.com/simonw/datasette/issues/292#issuecomment-392316673 | https://api.github.com/repos/simonw/datasette/issues/292 | MDEyOklzc3VlQ29tbWVudDM5MjMxNjY3Mw== | simonw 9599 | 2018-05-27T09:08:06Z | 2018-05-27T09:08:06Z | OWNER | Open question: how should this affect the row page? Just because columns were hidden on the table page doesn't necessarily mean they should be hidden on the row page as well. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for customizing the SQL used to select specific columns in the table view 326800219 |
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]);
user 1