issue_comments
6 rows where author_association = "NONE" and user = 4399499 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
user 1
- ocdtrekkie · 6 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1315814786 | https://github.com/simonw/datasette/issues/1892#issuecomment-1315814786 | https://api.github.com/repos/simonw/datasette/issues/1892 | IC_kwDOBm6k_c5Obb2C | ocdtrekkie 4399499 | 2022-11-15T20:14:38Z | 2022-11-15T20:14:38Z | NONE | I have no particular point, I just want to say being around for the 1.0 release of Datasette seems historic and legendary to witness. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Merge 1.0-dev branch back to main 1450312343 | |
1291277913 | https://github.com/simonw/datasette/issues/1852#issuecomment-1291277913 | https://api.github.com/repos/simonw/datasette/issues/1852 | IC_kwDOBm6k_c5M91ZZ | ocdtrekkie 4399499 | 2022-10-26T00:26:11Z | 2022-10-26T00:26:11Z | NONE |
This is what we do for Sandstorm essentially and I fully agree it's the right way to do API tokens in multiuser systems. Constraints will definitely be important though. I know I want a token to submit error reports programmatically, but I wouldn't want that token to convey my right to delete tables and records, Little Bobby Tables is out there somewhere, and he's all grown up now. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default API token authentication mechanism 1421552095 | |
1289752130 | https://github.com/simonw/datasette/issues/1851#issuecomment-1289752130 | https://api.github.com/repos/simonw/datasette/issues/1851 | IC_kwDOBm6k_c5M4A5C | ocdtrekkie 4399499 | 2022-10-24T23:07:30Z | 2022-10-24T23:07:30Z | NONE | How are you tying the bearer token to identity? I'm excited to see this feature, and since Sandstorm controls API access using the same header, it also will transparently support the API documentation here, but we strip the bearer before the request reaches the app (replacing it with our existing auth headers, of course). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API to insert a single record into an existing table 1421544654 | |
1279846110 | https://github.com/simonw/datasette/issues/1845#issuecomment-1279846110 | https://api.github.com/repos/simonw/datasette/issues/1845 | IC_kwDOBm6k_c5MSObe | ocdtrekkie 4399499 | 2022-10-15T22:49:00Z | 2022-10-15T22:49:00Z | NONE | I think there's probably some core plugins a new user should just "get" maybe. I feel our Sandstorm package has really reasonable defaults, the ability to bring data in for instance. However, you also have to know that's in the hamburger menu, it's not necessarily intuitive where to start. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Reconsider the Datasette first-run experience 1410305897 | |
1271024708 | https://github.com/simonw/datasette/pull/1838#issuecomment-1271024708 | https://api.github.com/repos/simonw/datasette/issues/1838 | IC_kwDOBm6k_c5LwkxE | ocdtrekkie 4399499 | 2022-10-07T02:19:49Z | 2022-10-07T02:19:49Z | NONE | Ooh, I didn't even think about links in tables! You're definitely right on the approach to this. It might also be a really good "stupidly simple" plugin for me to try to build myself, which could be fun. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Open Datasette link in new tab 1400494162 | |
1242187519 | https://github.com/simonw/datasette/issues/1808#issuecomment-1242187519 | https://api.github.com/repos/simonw/datasette/issues/1808 | IC_kwDOBm6k_c5KCkb_ | ocdtrekkie 4399499 | 2022-09-09T16:22:19Z | 2022-09-09T16:22:19Z | NONE | @simonw Will upload_csvs treat that as a database it can import to if you set it as mutable? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Database() constructor currently defaults is_mutable to False 1368030952 |
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]);
issue 6