issue_comments
4 rows where "created_at" is on date 2019-12-08 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, updated_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
563001064 | https://github.com/simonw/datasette/issues/648#issuecomment-563001064 | https://api.github.com/repos/simonw/datasette/issues/648 | MDEyOklzc3VlQ29tbWVudDU2MzAwMTA2NA== | simonw 9599 | 2019-12-08T22:09:20Z | 2019-12-08T22:09:20Z | OWNER | Stretch goal: it would be neat if these pages could return custom HTTP headers (eg content-type) and maybe even status codes (eg for redirects) somehow. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for adding arbitrary pages like /about 534492501 | |
563000942 | https://github.com/simonw/datasette/issues/648#issuecomment-563000942 | https://api.github.com/repos/simonw/datasette/issues/648 | MDEyOklzc3VlQ29tbWVudDU2MzAwMDk0Mg== | simonw 9599 | 2019-12-08T22:08:14Z | 2019-12-08T22:08:14Z | OWNER | Alternative idea: a new concept of "pages" which live inside
This only takes effect on 404 errors from core Datasette. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for adding arbitrary pages like /about 534492501 | |
562940252 | https://github.com/simonw/datasette/issues/649#issuecomment-562940252 | https://api.github.com/repos/simonw/datasette/issues/649 | MDEyOklzc3VlQ29tbWVudDU2Mjk0MDI1Mg== | simonw 9599 | 2019-12-08T11:59:52Z | 2019-12-08T12:00:12Z | OWNER | The easiest solution would be to only show counts on the index pages for immutable ( I don't like this, because the most common uses of Datasette don't in my opinion justify it. Most of the time Datasette will be running against a single, small, mutable database. I'd like to show counts in that case. Some options:
Worth prototyping a bit to see what works best. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Reduce table counts on index page with many databases 534530973 | |
562913040 | https://github.com/simonw/datasette/issues/648#issuecomment-562913040 | https://api.github.com/repos/simonw/datasette/issues/648 | MDEyOklzc3VlQ29tbWVudDU2MjkxMzA0MA== | simonw 9599 | 2019-12-08T04:56:43Z | 2019-12-08T04:56:43Z | OWNER | Idea: do this with a simple template naming convention. If you hit |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mechanism for adding arbitrary pages like /about 534492501 |
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]);
issue 2