github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/datasette/issues/1653#issuecomment-1061150672 | https://api.github.com/repos/simonw/datasette/issues/1653 | 1061150672 | IC_kwDOBm6k_c4_P9_Q | 9599 | 2022-03-07T21:23:39Z | 2022-03-07T21:23:39Z | OWNER | There may be a short-term fix for this: table view could start accepting a `?_sort_sql=SQLfragment` parameter, similar to the `?_where=` parameter described here: https://docs.datasette.io/en/stable/json_api.html#special-table-arguments That fragment could then be pre-populated in `metadata`. Makes me think maybe that `?_where=` should be optionally settable in metadata too? | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1161937073 | |
https://github.com/simonw/datasette/issues/1653#issuecomment-1061148807 | https://api.github.com/repos/simonw/datasette/issues/1653 | 1061148807 | IC_kwDOBm6k_c4_P9iH | 9599 | 2022-03-07T21:21:23Z | 2022-03-07T21:21:23Z | OWNER | This is currently blocked on the fact that Datasette doesn't have a mechanism for sorting by more than one column: - #197 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
1161937073 |