issue_comments

Table actions

1 row where author_association = "OWNER" and "created_at" is on date 2023-01-19 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

author_association 1

  • OWNER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1397734424 https://github.com/simonw/datasette/issues/1989#issuecomment-1397734424 https://api.github.com/repos/simonw/datasette/issues/1989 IC_kwDOBm6k_c5TT7wY simonw 9599 2023-01-19T23:18:45Z 2023-01-19T23:18:45Z OWNER

There's a ?_nocol=x argument you can use to hide a column when you link to a table, but that won't help you if you need to hide the column for privacy reasons: https://docs.datasette.io/en/latest/json_api.html#special-table-arguments

One solution right now is to define a SQL view for the things that you DO want people to be able to see, and then use Datasette's permission system to hide the tables ('"allow": false in metadata for each table) but show the views.

If you want to redact specific columns there's a plugin for doing that: https://datasette.io/plugins/datasette-mask-columns

This does make sense as more of a core Datasette feature though - tagging it as a feature suggestion.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Suggestion: Hiding columns 1531991339  

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