issue_comments: 851115805
This data as json
| 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/1345#issuecomment-851115805 | https://api.github.com/repos/simonw/datasette/issues/1345 | 851115805 | MDEyOklzc3VlQ29tbWVudDg1MTExNTgwNQ== | 9599 | 2021-05-31T01:59:39Z | 2021-05-31T01:59:39Z | OWNER | Maybe there's a concept here of the columns that are required by a selected facet? Those can then be included as `data-` attributes on the page, which will then impact which "Hide this column" options are available. I can also use them to provide a better error message than "no such column: state" - I can verify that `?_nocol` and `?_col` have not been used to disable the required columns. There is one other option here: I could still include the columns that are known to be needed for faceting in the faceting SQL queries, but leave them out of the query that is used to return the results! That's actually a pretty tempting (albeit more complex) option. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 904071938 |