issue_comments

Table actions

4 rows where issue = 1374626873 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

author_association 2

issue 1

  • Featured table(s) on the homepage · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1248290151 https://github.com/simonw/datasette/issues/1810#issuecomment-1248290151 https://api.github.com/repos/simonw/datasette/issues/1810 IC_kwDOBm6k_c5KZ2Vn simonw 9599 2022-09-15T15:51:04Z 2022-09-15T15:51:25Z OWNER

I could prototype this idea as a datasette-featured-tables plugin that delivers its own custom index.html template.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Featured table(s) on the homepage 1374626873  
1248289857 https://github.com/simonw/datasette/issues/1810#issuecomment-1248289857 https://api.github.com/repos/simonw/datasette/issues/1810 IC_kwDOBm6k_c5KZ2RB simonw 9599 2022-09-15T15:50:46Z 2022-09-15T15:50:46Z OWNER

Idea: allow the user to specify one or more featured tables. Each table is then shown as a summary on the homepage - with the total number of rows and the first 5 rows. If the table has search configured there's a search box too.

If the instance has only one database with only one table (excluding hidden tables) it gets featured automatically perhaps (maybe with a way to opt-out of that if you want to).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Featured table(s) on the homepage 1374626873  
1248204219 https://github.com/simonw/datasette/issues/1810#issuecomment-1248204219 https://api.github.com/repos/simonw/datasette/issues/1810 IC_kwDOBm6k_c5KZhW7 psychemedia 82988 2022-09-15T14:44:47Z 2022-09-15T14:46:26Z CONTRIBUTOR

A couple+ of possible use case examples:

  • someone has a collection of articles indexed with FTS; they want to publish a simple search tool over the results;
  • someone has an image collection and they want to be able to search over description text to return images;
  • someone has a set of locations with descriptions, and wants to run a query over places and descriptions and get results as a listing or on a map;
  • someone has a set of audio or video files with titles, descriptions and/or transcripts, and wants to be able to search over them and return playable versions of returned items.

In many cases, I suspect the raw content will be in one table, but the search table will be a second (eg FTS) table. Generally, the search may be over one or more joined tables, and the results constructed from one or more tables (which may or may not be distinct from the search tables).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Featured table(s) on the homepage 1374626873  
1248187089 https://github.com/simonw/datasette/issues/1810#issuecomment-1248187089 https://api.github.com/repos/simonw/datasette/issues/1810 IC_kwDOBm6k_c5KZdLR simonw 9599 2022-09-15T14:31:36Z 2022-09-15T14:31:36Z OWNER

Twitter conversation that inspired this issue: https://twitter.com/psychemedia/status/1570410108785684481

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Featured table(s) on the homepage 1374626873  

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