issue_comments

Table actions

1 row where issue = 447451492 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • simonw · 1 ✖

issue 1

  • Mechanism for displaying summary of m2m relationships in rows on table view · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
495068273 https://github.com/simonw/datasette/issues/484#issuecomment-495068273 https://api.github.com/repos/simonw/datasette/issues/484 MDEyOklzc3VlQ29tbWVudDQ5NTA2ODI3Mw== simonw 9599 2019-05-23T05:03:48Z 2019-05-23T05:04:35Z OWNER

Ideally we would display a limited number of m2m related records with a "..." if there are more than our limit. I could also show a count of the total number of records, but this would have to be agressively time-limited or it could cause extremely poor performance.

This could be implemented as a SQL query for every displayed row, taking advantage of Many Small Queries Are Efficient In SQLite. Provided that SQL runs against an index this should be fast to display even on a table with hundreds of rows.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Mechanism for displaying summary of m2m relationships in rows on table view 447451492  

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