issue_comments
12 rows where author_association = "OWNER", "created_at" is on date 2022-01-13, reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 12 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1012583091 | https://github.com/simonw/datasette/issues/1590#issuecomment-1012583091 | https://api.github.com/repos/simonw/datasette/issues/1590 | IC_kwDOBm6k_c48Wsqz | simonw 9599 | 2022-01-13T22:41:15Z | 2022-01-13T22:41:15Z | OWNER | Seeing as this area of the code has produced so many bugs in the past, I think part of the fix may be to write comprehensive documentation about how routing works for the internals documentation. Doing so might help me figure this bug out! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Table+query JSON and CSV links broken when using `base_url` setting 1099723916 | |
1012575013 | https://github.com/simonw/datasette/issues/1595#issuecomment-1012575013 | https://api.github.com/repos/simonw/datasette/issues/1595 | IC_kwDOBm6k_c48Wqsl | simonw 9599 | 2022-01-13T22:29:22Z | 2022-01-13T22:29:22Z | OWNER | Most of these are already written for these two alpha releases: - https://github.com/simonw/datasette/releases/tag/0.60a0 - https://github.com/simonw/datasette/releases/tag/0.60a1 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release notes for 0.60 1102484126 | |
1012554208 | https://github.com/simonw/datasette/issues/1588#issuecomment-1012554208 | https://api.github.com/repos/simonw/datasette/issues/1588 | IC_kwDOBm6k_c48Wlng | simonw 9599 | 2022-01-13T22:07:15Z | 2022-01-13T22:07:15Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`explain query plan select` is too strict about whitespace 1097101917 | ||
1012552760 | https://github.com/simonw/datasette/issues/650#issuecomment-1012552760 | https://api.github.com/repos/simonw/datasette/issues/650 | IC_kwDOBm6k_c48WlQ4 | simonw 9599 | 2022-01-13T22:04:56Z | 2022-01-13T22:04:56Z | OWNER | Challenge: explain the difference between view as in SQL view, and view as in the code that serves |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add a glossary to the documentation 534629631 | |
1012546924 | https://github.com/simonw/datasette/issues/1336#issuecomment-1012546924 | https://api.github.com/repos/simonw/datasette/issues/1336 | IC_kwDOBm6k_c48Wj1s | simonw 9599 | 2022-01-13T21:55:58Z | 2022-01-13T21:55:58Z | OWNER | See also: - #1412 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Document turning on WAL for live served SQLite databases 895686039 | |
1012546223 | https://github.com/simonw/datasette/issues/1466#issuecomment-1012546223 | https://api.github.com/repos/simonw/datasette/issues/1466 | IC_kwDOBm6k_c48Wjqv | simonw 9599 | 2022-01-13T21:54:51Z | 2022-01-13T21:54:51Z | OWNER | Going with this for the copy:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add Datasette Desktop to installation documentation 991467558 | |
1012536257 | https://github.com/simonw/datasette/issues/1594#issuecomment-1012536257 | https://api.github.com/repos/simonw/datasette/issues/1594 | IC_kwDOBm6k_c48WhPB | simonw 9599 | 2022-01-13T21:38:48Z | 2022-01-13T21:38:48Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add a CLI reference page to the docs, inspired by sqlite-utils 1102359726 | ||
1012535024 | https://github.com/simonw/datasette/issues/1594#issuecomment-1012535024 | https://api.github.com/repos/simonw/datasette/issues/1594 | IC_kwDOBm6k_c48Wg7w | simonw 9599 | 2022-01-13T21:36:53Z | 2022-01-13T21:36:53Z | OWNER | I went with a simpler pattern that |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add a CLI reference page to the docs, inspired by sqlite-utils 1102359726 | |
1012508787 | https://github.com/simonw/datasette/issues/1594#issuecomment-1012508787 | https://api.github.com/repos/simonw/datasette/issues/1594 | IC_kwDOBm6k_c48Wahz | simonw 9599 | 2022-01-13T20:56:14Z | 2022-01-13T20:56:34Z | OWNER | The implementation can be almost exactly the same as this: https://github.com/simonw/sqlite-utils/blame/74586d3cb26fa3cc3412721985ecdc1864c2a31d/docs/cli-reference.rst#L11-L76 I need to do something extra to ensure the output of |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add a CLI reference page to the docs, inspired by sqlite-utils 1102359726 | |
1012506595 | https://github.com/simonw/datasette/issues/1591#issuecomment-1012506595 | https://api.github.com/repos/simonw/datasette/issues/1591 | IC_kwDOBm6k_c48WZ_j | simonw 9599 | 2022-01-13T20:52:56Z | 2022-01-13T20:52:56Z | OWNER | You can already run Or I could even have available plugin settings show up as a list at the bottom of the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Maybe let plugins define custom serve options? 1100015398 | |
1012505706 | https://github.com/simonw/datasette/issues/1591#issuecomment-1012505706 | https://api.github.com/repos/simonw/datasette/issues/1591 | IC_kwDOBm6k_c48WZxq | simonw 9599 | 2022-01-13T20:51:30Z | 2022-01-13T20:51:30Z | OWNER | Another option: if I make plugin settings a higher level concept in Datasette than they are at the moment, I could allow them to be set either using I want to make changes to that anyway, because I'm increasingly uncomfortable with plugin settings ending up in the "metadata" mechanism. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Maybe let plugins define custom serve options? 1100015398 | |
1012504251 | https://github.com/simonw/datasette/issues/1591#issuecomment-1012504251 | https://api.github.com/repos/simonw/datasette/issues/1591 | IC_kwDOBm6k_c48WZa7 | simonw 9599 | 2022-01-13T20:49:19Z | 2022-01-13T20:49:59Z | OWNER | I try to stick pretty closely to what Click supports, and Click likes you to define options explicitly so that it can display them in the output of But... that makes me think that actually showing these options in The alternative would be to allow plugins to register their extra options with the command - which would mean the help output could look like this instead:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Maybe let plugins define custom serve options? 1100015398 |
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 8