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/767#issuecomment-632555800 | https://api.github.com/repos/simonw/datasette/issues/767 | 632555800 | MDEyOklzc3VlQ29tbWVudDYzMjU1NTgwMA== | 2657547 | 2020-05-22T08:00:23Z | 2020-05-22T08:00:23Z | CONTRIBUTOR | That would be perfect! | {
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
620969465 | |
| https://github.com/simonw/datasette/issues/767#issuecomment-632398475 | https://api.github.com/repos/simonw/datasette/issues/767 | 632398475 | MDEyOklzc3VlQ29tbWVudDYzMjM5ODQ3NQ== | 9599 | 2020-05-21T23:36:00Z | 2020-05-21T23:36:00Z | OWNER | Interesting. So this would take effect exclusively on pages that link to the queries, which I think just means this page: https://latest.datasette.io/fixtures How about this for the design: there's a new optional key in the metadata configuration for a query called `"fragment"` - used like this: ```json { "databases": { "fixtures": { "queries": { "neighborhood_search": { "sql": "\nselect neighborhood, facet_cities.name, state\nfrom facetable\n join facet_cities\n on facetable.city_id = facet_cities.id\nwhere neighborhood like '%' || :text || '%'\norder by neighborhood;\n", "title": "Search neighborhoods", "description_html": "<b>Demonstrating</b> simple like search", "name": "neighborhood_search", "fragment": "sql-format" } } } } } ``` Because of the `"fragment": "sql-format"` bit there the link to that query from https://latest.datasette.io/fixtures would be to `https://latest.datasette.io/fixtures/neighborhood_search#sql-format`. Does that cover what you need here? Have I missed anything? | {
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
620969465 |