issue_comments
21 rows where author_association = "OWNER", "created_at" is on date 2022-11-29 and reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw 21
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
1331432223 | https://github.com/simonw/datasette/issues/1915#issuecomment-1331432223 | https://api.github.com/repos/simonw/datasette/issues/1915 | IC_kwDOBm6k_c5PXAsf | simonw 9599 | 2022-11-29T23:06:17Z | 2022-11-29T23:06:17Z | OWNER | To (slightly) discourage abuse I'm going to make the demo database only visible to the root user - so people can't create tables with rude names and have them show to the public on https://latest.datasette.io/ |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Interactive demo of Datasette 1.0 write APIs 1468709531 | |
1331331082 | https://github.com/simonw/datasette/issues/1915#issuecomment-1331331082 | https://api.github.com/repos/simonw/datasette/issues/1915 | IC_kwDOBm6k_c5PWoAK | simonw 9599 | 2022-11-29T21:24:59Z | 2022-11-29T21:34:53Z | OWNER | Maybe a plugin called |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Interactive demo of Datasette 1.0 write APIs 1468709531 | |
1331238841 | https://github.com/simonw/datasette/issues/1850#issuecomment-1331238841 | https://api.github.com/repos/simonw/datasette/issues/1850 | IC_kwDOBm6k_c5PWRe5 | simonw 9599 | 2022-11-29T20:11:20Z | 2022-11-29T20:11:20Z | OWNER | Released this in Datasette 1.0a0: - #1913 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Write API in Datasette core 1421529723 | |
1331238029 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331238029 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWRSN | simonw 9599 | 2022-11-29T20:10:35Z | 2022-11-29T20:10:35Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | ||
1331226346 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331226346 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWObq | simonw 9599 | 2022-11-29T20:00:16Z | 2022-11-29T20:00:36Z | OWNER | Looks like a fix is coming: https://github.com/pypa/twine/issues/940#issuecomment-1331225509
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | |
1331225277 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331225277 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWOK9 | simonw 9599 | 2022-11-29T19:59:14Z | 2022-11-29T19:59:34Z | OWNER | I deleted the tag and tried creating a new release. Now running here: https://github.com/simonw/datasette/actions/runs/3577554546 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | |
1331216652 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331216652 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWMEM | simonw 9599 | 2022-11-29T19:54:22Z | 2022-11-29T19:54:22Z | OWNER | Filed a bug report here: https://bugs.launchpad.net/pkginfo/+bug/1998249 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | |
1331208206 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331208206 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWKAO | simonw 9599 | 2022-11-29T19:51:31Z | 2022-11-29T19:51:31Z | OWNER | https://pypi.org/project/pkginfo/#history - 1.9.0 came out 39 minutes ago! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | |
1331207334 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331207334 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWJym | simonw 9599 | 2022-11-29T19:50:37Z | 2022-11-29T19:50:37Z | OWNER | https://pypi.org/project/setuptools/65.6.3/ came out most recently - 23rd November (wheel and twine are older). No search results at all for that error message. This is very weird, I would have expected it to have been reported by now. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | |
1331205613 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331205613 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWJXt | simonw 9599 | 2022-11-29T19:48:52Z | 2022-11-29T19:48:52Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | ||
1331204360 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331204360 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWJEI | simonw 9599 | 2022-11-29T19:47:40Z | 2022-11-29T19:47:40Z | OWNER | ... but the last step of the deploy failed, when it was meant to push to PyPI!
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | |
1331203997 | https://github.com/simonw/datasette/issues/1913#issuecomment-1331203997 | https://api.github.com/repos/simonw/datasette/issues/1913 | IC_kwDOBm6k_c5PWI-d | simonw 9599 | 2022-11-29T19:47:13Z | 2022-11-29T19:47:13Z | OWNER | Weird, retrying the tests DID get them to pass. https://github.com/simonw/datasette/actions/runs/3577355358/jobs/6016518244 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release Datasette 1.0a0 1468603401 | |
1331201207 | https://github.com/simonw/datasette/issues/1877#issuecomment-1331201207 | https://api.github.com/repos/simonw/datasette/issues/1877 | IC_kwDOBm6k_c5PWIS3 | simonw 9599 | 2022-11-29T19:44:07Z | 2022-11-29T19:44:07Z | OWNER | I fixed the duplicate logic issue here: https://github.com/simonw/datasette/commit/ee64130fa8a5ff4a24791916c696e10cf2375102
Decided not to address |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Refactor and tidy up final write API code 1432012302 | |
1331196531 | https://github.com/simonw/datasette/pull/1912#issuecomment-1331196531 | https://api.github.com/repos/simonw/datasette/issues/1912 | IC_kwDOBm6k_c5PWHJz | simonw 9599 | 2022-11-29T19:39:10Z | 2022-11-29T19:39:10Z | OWNER | Annoyingly it looks like I can't rebase this one, and I don't want to squash-merge and lose the commits, so I'm going to do a regular merge instead. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Merge 1.0-dev (with initial write API) back into main 1468592292 | |
1331181922 | https://github.com/simonw/datasette/issues/1891#issuecomment-1331181922 | https://api.github.com/repos/simonw/datasette/issues/1891 | IC_kwDOBm6k_c5PWDli | simonw 9599 | 2022-11-29T19:23:41Z | 2022-11-29T19:23:41Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1.0a0 release notes 1450303205 | ||
1331143292 | https://github.com/simonw/datasette/issues/1891#issuecomment-1331143292 | https://api.github.com/repos/simonw/datasette/issues/1891 | IC_kwDOBm6k_c5PV6J8 | simonw 9599 | 2022-11-29T18:57:40Z | 2022-11-29T18:57:40Z | OWNER | I'm going to keep these short - they'll mostly be links to the documentation for the new features. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1.0a0 release notes 1450303205 | |
1331140747 | https://github.com/simonw/datasette/issues/1891#issuecomment-1331140747 | https://api.github.com/repos/simonw/datasette/issues/1891 | IC_kwDOBm6k_c5PV5iL | simonw 9599 | 2022-11-29T18:55:42Z | 2022-11-29T18:55:42Z | OWNER | All features for the alpha are complete now. Release notes should be based on these commits: https://github.com/simonw/datasette/compare/0.63.2...6bda2257868a2cbd70b84b7a86a5bcb47dcc4874 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1.0a0 release notes 1450303205 | |
1331135709 | https://github.com/simonw/datasette/issues/1911#issuecomment-1331135709 | https://api.github.com/repos/simonw/datasette/issues/1911 | IC_kwDOBm6k_c5PV4Td | simonw 9599 | 2022-11-29T18:50:58Z | 2022-11-29T18:50:58Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`/db/-/create` should support creating tables with compound primary keys 1468519699 | ||
1331120055 | https://github.com/simonw/datasette/issues/1911#issuecomment-1331120055 | https://api.github.com/repos/simonw/datasette/issues/1911 | IC_kwDOBm6k_c5PV0e3 | simonw 9599 | 2022-11-29T18:36:01Z | 2022-11-29T18:36:01Z | OWNER | Current API design:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`/db/-/create` should support creating tables with compound primary keys 1468519699 | |
1331089156 | https://github.com/simonw/datasette/issues/1863#issuecomment-1331089156 | https://api.github.com/repos/simonw/datasette/issues/1863 | IC_kwDOBm6k_c5PVs8E | simonw 9599 | 2022-11-29T18:08:53Z | 2022-11-29T18:08:53Z | OWNER | I do think this needs type checking - I just tried and you really can send a string to an integer column and have it work, which feels bad. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Update a single record in an existing table 1425029242 | |
1330974099 | https://github.com/simonw/datasette/issues/1863#issuecomment-1330974099 | https://api.github.com/repos/simonw/datasette/issues/1863 | IC_kwDOBm6k_c5PVQ2T | simonw 9599 | 2022-11-29T17:03:00Z | 2022-11-29T17:11:05Z | OWNER | I've decided that I won't do that validation for the first version of this - I'm going to teach |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Update a single record in an existing table 1425029242 |
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 8