{"id": "sql_queries:fragment", "page": "sql_queries", "ref": "fragment", "title": "fragment", "content": "Some plugins, such as  datasette-vega , can be configured by including additional data in the fragment hash of the URL - the bit that comes after a  #  symbol. \n                     You can set a default fragment hash that will be included in the link to the canned query from the database index page using the  \"fragment\"  key. \n                     This example demonstrates both  fragment  and  hide_sql : \n                     [[[cog\nconfig_example(cog, \"\"\"\ndatabases:\n  fixtures:\n    queries:\n      neighborhood_search:\n        fragment: fragment-goes-here\n        hide_sql: true\n        sql: |-\n          select neighborhood, facet_cities.name, state\n          from facetable join facet_cities on facetable.city_id = facet_cities.id\n          where neighborhood like '%' || :text || '%' order by neighborhood;\n\"\"\") \n                     ]]] \n                     [[[end]]] \n                     See here  for a demo of this in action.", "breadcrumbs": "[\"Running SQL queries\", \"Canned queries\", \"Additional canned query options\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette-vega\", \"label\": \"datasette-vega\"}, {\"href\": \"https://latest.datasette.io/fixtures#queries\", \"label\": \"See here\"}]"}
{"id": "sql_queries:hide-sql", "page": "sql_queries", "ref": "hide-sql", "title": "hide_sql", "content": "Canned queries default to displaying their SQL query at the top of the page. If the query is extremely long you may want to hide it by default, with a \"show\" link that can be used to make it visible. \n                     Add the  \"hide_sql\": true  option to hide the SQL query by default.", "breadcrumbs": "[\"Running SQL queries\", \"Canned queries\", \"Additional canned query options\"]", "references": "[]"}