issue_comments

Table actions

1 row where author_association = "CONTRIBUTOR", issue = 1552368054 and user = 193185 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

  • cldellow · 1 ✖

issue 1

  • rewrite_sql hook · 1 ✖

author_association 1

  • CONTRIBUTOR · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1399847946 https://github.com/simonw/datasette/issues/2000#issuecomment-1399847946 https://api.github.com/repos/simonw/datasette/issues/2000 IC_kwDOBm6k_c5Tb_wK cldellow 193185 2023-01-23T06:08:00Z 2023-01-23T06:08:00Z CONTRIBUTOR

Actually, I discovered your post showing how a plugin can add a Datasette hook. That's wild! I've released datasette-rewrite-sql that adds this ability, albeit via monkey patching.

I had hoped to be able to expose request to the hook (or, even better actor) when the SQL was being run as a result of a user's HTTP request.

But some spelunking in the code makes me suspect that would actually require co-operation from Datasette itself. I'd be happy to be wrong and pointed in the right direction, though!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 rewrite_sql hook 1552368054  

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