issue_comments

Table actions

2 rows where issue = 314847571 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

  • Investigate syntactic sugar for plugins · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
642944645 https://github.com/simonw/datasette/issues/220#issuecomment-642944645 https://api.github.com/repos/simonw/datasette/issues/220 MDEyOklzc3VlQ29tbWVudDY0Mjk0NDY0NQ== simonw 9599 2020-06-11T21:49:55Z 2020-06-11T21:49:55Z OWNER

I'm OK with not implementing this - I've got used to the existing mechanism, and it doesn't frustrate me enough to work on this more.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Investigate syntactic sugar for plugins 314847571  
381777108 https://github.com/simonw/datasette/issues/220#issuecomment-381777108 https://api.github.com/repos/simonw/datasette/issues/220 MDEyOklzc3VlQ29tbWVudDM4MTc3NzEwOA== simonw 9599 2018-04-16T23:04:04Z 2018-04-16T23:04:04Z OWNER

This could also help workaround the current predicament that a single plugin can only define one prepare_connection hook.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Investigate syntactic sugar for plugins 314847571  

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