issue_comments
5 rows where issue = 508070977
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
542872267 | https://github.com/simonw/datasette/issues/597#issuecomment-542872267 | https://api.github.com/repos/simonw/datasette/issues/597 | MDEyOklzc3VlQ29tbWVudDU0Mjg3MjI2Nw== | simonw 9599 | 2019-10-16T20:13:21Z | 2019-10-16T20:13:21Z | OWNER | ``` $ echo '{"hello": "world"}' | sqlite-utils insert foo.db hello - $ echo '{"hello": "world"}' | sqlite-utils insert foo-bar.db hello - $ datasette publish now \ --about_url=https://github.com/simonw/datasette/issues/597 \ --title="Issue #597" \ --alias=datasette-issue-597 \ foo.db foo-bar.db ``` This failed to replicate the issue. https://datasette-issue-597.now.sh/ is working as it should. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | If you have databases called foo.db and foo-bar.db you cannot visit /foo-bar 508070977 | |
542872388 | https://github.com/simonw/datasette/issues/597#issuecomment-542872388 | https://api.github.com/repos/simonw/datasette/issues/597 | MDEyOklzc3VlQ29tbWVudDU0Mjg3MjM4OA== | simonw 9599 | 2019-10-16T20:13:38Z | 2019-10-16T20:13:38Z | OWNER | I encountered this bug in my own private instance of Datasette running behind an nginx proxy. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | If you have databases called foo.db and foo-bar.db you cannot visit /foo-bar 508070977 | |
543389140 | https://github.com/simonw/datasette/issues/597#issuecomment-543389140 | https://api.github.com/repos/simonw/datasette/issues/597 | MDEyOklzc3VlQ29tbWVudDU0MzM4OTE0MA== | simonw 9599 | 2019-10-17T22:34:57Z | 2019-10-17T22:34:57Z | OWNER | I've managed to replicate the bug again in my private instance, using databases called `twitter.db` and `twitter-bug.db`. When I visit `/twitter-bug` I see (but I am not redirected to) the `/twitter` page. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | If you have databases called foo.db and foo-bar.db you cannot visit /foo-bar 508070977 | |
543389950 | https://github.com/simonw/datasette/issues/597#issuecomment-543389950 | https://api.github.com/repos/simonw/datasette/issues/597 | MDEyOklzc3VlQ29tbWVudDU0MzM4OTk1MA== | simonw 9599 | 2019-10-17T22:37:41Z | 2019-10-17T22:37:41Z | OWNER | Aha! It turns out my attempt to replicate the bug DID work: https://datasette-issue-597.now.sh/foo-bar <img width="742" alt="foo" src="https://user-images.githubusercontent.com/9599/67052770-0babb680-f0f4-11e9-86c7-487b42783394.png"> | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | If you have databases called foo.db and foo-bar.db you cannot visit /foo-bar 508070977 | |
543900283 | https://github.com/simonw/datasette/issues/597#issuecomment-543900283 | https://api.github.com/repos/simonw/datasette/issues/597 | MDEyOklzc3VlQ29tbWVudDU0MzkwMDI4Mw== | simonw 9599 | 2019-10-18T19:25:57Z | 2019-10-18T19:27:06Z | OWNER | I'm suspicious of this code here: https://github.com/simonw/datasette/blob/b6ad1fdc7068cb8248787843e7438d1f19fa2e3a/datasette/views/base.py#L193-L205 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | If you have databases called foo.db and foo-bar.db you cannot visit /foo-bar 508070977 |
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]);