issue_comments

Table actions

1 row where issue = 476852861 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

issue 1

  • Add database_color as a configurable option · 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
1674223722 https://github.com/simonw/datasette/issues/568#issuecomment-1674223722 https://api.github.com/repos/simonw/datasette/issues/568 IC_kwDOBm6k_c5jyqBq simonw 9599 2023-08-11T05:19:42Z 2023-08-11T05:19:42Z OWNER

I decided not to implement this yet, because making database.color dependent on metadata interferes with my goal to eventually make metadata lookups async in order to serve them better from plugins.

I'll leave this issue open though as it may get solved in future redesigns of the metadata system, refs:

  • 1384

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add database_color as a configurable option 476852861  

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