issue_comments

Table actions

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

  • It would be more intuitive if "allow": none meant "no-one can do this" · 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
642324847 https://github.com/simonw/datasette/issues/831#issuecomment-642324847 https://api.github.com/repos/simonw/datasette/issues/831 MDEyOklzc3VlQ29tbWVudDY0MjMyNDg0Nw== simonw 9599 2020-06-10T23:50:55Z 2020-06-10T23:50:55Z OWNER

Actually I'm not sure about this. If "allow": null means "no-one can do this", what's the allow block syntax for "everyone can do this"?

It could be "allow": {} - but that's not intuitive because normally the allow block shows keys that need to match. {} suggests to me that no matches are possible.

So I think I'm going to stick with the current mechanism, which is that "allow": null means "anyone can do this" and "allow": {} means "no-one can do this".

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 It would be more intuitive if "allow": none meant "no-one can do this" 636614868  

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