issue_comments

Table actions

5 rows where issue = 1114147905

✖
✖

✎ View and edit SQL

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
1021413700 https://github.com/simonw/datasette/issues/1612#issuecomment-1021413700 https://api.github.com/repos/simonw/datasette/issues/1612 IC_kwDOBm6k_c484YlE simonw 9599 2022-01-25T17:07:29Z 2022-01-25T17:07:29Z OWNER That's a much better place for them, I like this idea. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Move canned queries closer to the SQL input area 1114147905  
1021472918 https://github.com/simonw/datasette/issues/1612#issuecomment-1021472918 https://api.github.com/repos/simonw/datasette/issues/1612 IC_kwDOBm6k_c484nCW simonw 9599 2022-01-25T18:14:27Z 2022-01-25T18:15:54Z OWNER They're currently shown at the very bottom of the page, under the list of tables and far away from the SQL query box: https://latest.datasette.io/fixtures <img width="353" alt="image" src="https://user-images.githubusercontent.com/9599/151034640-c3b79214-7fec-4137-b3ed-45541167feff.png"> I'm also questioning if "Queries" is the best header for this. Other options: - **Canned queries** (what the feature is called in the documentation, but I don't think it's a great user-facing term) - **Saved queries** - overlaps with a mechanism by which queries can be saved by the user using a plugin such as [datasette-saved-queries](https://github.com/simonw/datasette-saved-queries) - though that plugin does itself use the canned queries plugin hook so not completely unrelated - **Sample or Example queries** - I don't like these much because they're more than just examples - they are often the core functionality of the specific customized Datasette instance - **Prepared queries** - overlaps with terminology used in other databases, so not great either - **Pre-configured queries** - urgh, don't like that language, feels clumsy - **Query recipes** - bit out of left-field this one, only really makes sense for queries that include named parameters for specific use-cases Maybe "Queries" is right after all. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Move canned queries closer to the SQL input area 1114147905  
1021477220 https://github.com/simonw/datasette/issues/1612#issuecomment-1021477220 https://api.github.com/repos/simonw/datasette/issues/1612 IC_kwDOBm6k_c484oFk simonw 9599 2022-01-25T18:19:31Z 2022-01-25T18:19:31Z OWNER Here's something I like: I also added a "Tables" `<h2>` heading and bumped the tables themselves down from a `<h2>` to a `<h3>`: <img width="909" alt="image" src="https://user-images.githubusercontent.com/9599/151035671-9920db99-a943-46a6-8cd8-7a0ad7524474.png"> {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Move canned queries closer to the SQL input area 1114147905  
1021489826 https://github.com/simonw/datasette/issues/1612#issuecomment-1021489826 https://api.github.com/repos/simonw/datasette/issues/1612 IC_kwDOBm6k_c484rKi simonw 9599 2022-01-25T18:34:21Z 2022-01-25T18:34:21Z OWNER OK, that's live on https://latest.datasette.io/fixtures now - I really like it. Thanks for the suggestion! {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Move canned queries closer to the SQL input area 1114147905  
1021497165 https://github.com/simonw/datasette/issues/1612#issuecomment-1021497165 https://api.github.com/repos/simonw/datasette/issues/1612 IC_kwDOBm6k_c484s9N jsfenfen 639012 2022-01-25T18:44:23Z 2022-01-25T18:44:23Z CONTRIBUTOR OMG, this might be the fastest OS ticket I've ever filed, thanks so much @simonw {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Move canned queries closer to the SQL input area 1114147905  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);