issue_comments
1 row where "updated_at" is on date 2020-08-26 sorted by performed_via_github_app
This data as json, CSV (advanced)
created_at (date) 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app ▼ |
---|---|---|---|---|---|---|---|---|---|---|---|
680374196 | https://github.com/simonw/datasette/issues/950#issuecomment-680374196 | https://api.github.com/repos/simonw/datasette/issues/950 | MDEyOklzc3VlQ29tbWVudDY4MDM3NDE5Ng== | simonw 9599 | 2020-08-26T00:43:50Z | 2020-08-26T00:43:50Z | OWNER | The problem with the term "private" is that it could be confused with the concept of databases that aren't visible to the public due to the permissions system - the ones that are displayed with the padlock icon e.g. on https://datasette-auth-passwords-demo.datasette.io/ <img width="595" alt="datasette-auth-passwords_demo__public__private" src="https://user-images.githubusercontent.com/9599/91241752-807b5400-e6fa-11ea-9f71-9da37c371b45.png"> So I think "secret" is a better term for these. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Private/secret databases: database files that are only visible to plugins 685806511 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
updated_at (date) 1 ✖