{"html_url": "https://github.com/simonw/datasette/issues/446#issuecomment-702459432", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/446", "id": 702459432, "node_id": "MDEyOklzc3VlQ29tbWVudDcwMjQ1OTQzMg==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2020-10-02T00:08:47Z", "updated_at": "2020-10-02T00:08:47Z", "author_association": "OWNER", "body": "I've decided not to bother with this, especially having redesigned some hooks to return Datasette standard `Response` objects.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 440134714, "label": "Define mechanism for plugins to return structured data"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/565#issuecomment-702459747", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/565", "id": 702459747, "node_id": "MDEyOklzc3VlQ29tbWVudDcwMjQ1OTc0Nw==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2020-10-02T00:09:55Z", "updated_at": "2020-10-02T00:09:55Z", "author_association": "OWNER", "body": "Today Datasette uses `\"click~=7.1.1\"` and Uvicorn uses `\"click==7.*\"` so I think we are OK.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 473307794, "label": "Conflict between datasette and uvicorn click versions"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/778#issuecomment-702493047", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/778", "id": 702493047, "node_id": "MDEyOklzc3VlQ29tbWVudDcwMjQ5MzA0Nw==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2020-10-02T02:26:25Z", "updated_at": "2020-10-02T02:26:25Z", "author_association": "OWNER", "body": "I think this could work for arbitrary SQL queries too. Those would need querystring configuration that specifies which sorted column(s) should be used for the \"next\" cursor.\r\n\r\nOne example: I'd like to be able to offer a paginated list of counts of values in a table - e.g. this query:\r\n\r\nhttps://fivethirtyeight.datasettes.com/fivethirtyeight?sql=select+replies%2C+count%28*%29+from+%5Btwitter-ratio%2Fsenators%5D+group+by+replies+order+by+count%28*%29+desc%3B\r\n\r\nThat could even become a query that gets linked to from the column actions menu.", "reactions": "{\"total_count\": 1, \"+1\": 1, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 626211658, "label": "Ability to configure keyset pagination for views and queries"}, "performed_via_github_app": null}