issue_comments

Table actions

2 rows where author_association = "OWNER", issue = 792931244 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • simonw · 2 ✖

issue 1

  • Documentation convention for marking unstable APIs. · 2 ✖

author_association 1

  • OWNER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
766464136 https://github.com/simonw/datasette/issues/1202#issuecomment-766464136 https://api.github.com/repos/simonw/datasette/issues/1202 MDEyOklzc3VlQ29tbWVudDc2NjQ2NDEzNg== simonw 9599 2021-01-25T00:01:02Z 2021-01-25T00:01:02Z OWNER

I'm going to use the existing .. warning:: pattern for this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Documentation convention for marking unstable APIs. 792931244  
766462475 https://github.com/simonw/datasette/issues/1202#issuecomment-766462475 https://api.github.com/repos/simonw/datasette/issues/1202 MDEyOklzc3VlQ29tbWVudDc2NjQ2MjQ3NQ== simonw 9599 2021-01-24T23:49:28Z 2021-01-24T23:50:33Z OWNER

Can use an "admonition" similar to this: sphinx .. warning:: Restricting access to tables and views in this way will NOT prevent users from querying them using arbitrary SQL queries, `like this <https://latest.datasette.io/fixtures?sql=select+*+from+facetable>`__ for example. As seen on https://docs.datasette.io/en/stable/authentication.html#controlling-access-to-specific-tables-and-views

Documentation: https://docutils.sourceforge.io/docs/ref/rst/directives.html#specific-admonitions

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Documentation convention for marking unstable APIs. 792931244  

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