issue_comments

Table actions

4 rows where author_association = "OWNER", issue = 1114147905 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • simonw · 4 ✖

issue 1

  • Move canned queries closer to the SQL input area · 4 ✖

author_association 1

  • OWNER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
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  
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>:

 
{
    "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

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 - 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  
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  

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