{"id": "changelog:id68", "page": "changelog", "ref": "id68", "title": "0.35 (2020-02-04)", "content": "Added five new plugins and one new conversion tool to the  The Datasette Ecosystem . \n                 \n                 \n                     The  Datasette  class has a new  render_template()  method which can be used by plugins to render templates using Datasette's pre-configured  Jinja  templating library. \n                 \n                 \n                     You can now execute SQL queries that start with a  -- comment  - thanks, Jay Graves ( #653 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://jinja.palletsprojects.com/\", \"label\": \"Jinja\"}, {\"href\": \"https://github.com/simonw/datasette/pull/653\", \"label\": \"#653\"}]"}
{"id": "changelog:id69", "page": "changelog", "ref": "id69", "title": "0.34 (2020-01-29)", "content": "_search=  queries are now correctly escaped using a new  escape_fts()  custom SQL function. This means you can now run searches for strings like  park.  without seeing errors. ( #651 ) \n                 \n                 \n                     Google Cloud Run  is no longer in beta, so  datasette publish cloudrun  has been updated to work even if the user has not installed the  gcloud  beta components package. Thanks, Katie McLaughlin ( #660 ) \n                 \n                 \n                     datasette package  now accepts a  --port  option for specifying which port the resulting Docker container should listen on. ( #661 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/651\", \"label\": \"#651\"}, {\"href\": \"https://cloud.google.com/run/\", \"label\": \"Google Cloud Run\"}, {\"href\": \"https://github.com/simonw/datasette/pull/660\", \"label\": \"#660\"}, {\"href\": \"https://github.com/simonw/datasette/issues/661\", \"label\": \"#661\"}]"}
{"id": "changelog:id7", "page": "changelog", "ref": "id7", "title": "0.64.1 (2023-01-11)", "content": "Documentation now links to a current source of information for installing Python 3. ( #1987 ) \n                 \n                 \n                     Incorrectly calling the Datasette constructor using  Datasette(\"path/to/data.db\")  instead of  Datasette([\"path/to/data.db\"])  now returns a useful error message. ( #1985 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1987\", \"label\": \"#1987\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1985\", \"label\": \"#1985\"}]"}
{"id": "changelog:id70", "page": "changelog", "ref": "id70", "title": "0.33 (2019-12-22)", "content": "rowid  is now included in dropdown menus for filtering tables ( #636 ) \n                 \n                 \n                     Columns are now only suggested for faceting if they have at least one value with more than one record ( #638 ) \n                 \n                 \n                     Queries with no results now display \"0 results\" ( #637 ) \n                 \n                 \n                     Improved documentation for the  --static  option ( #641 ) \n                 \n                 \n                     asyncio task information is now included on the  /-/threads  debug page \n                 \n                 \n                     Bumped Uvicorn dependency 0.11 \n                 \n                 \n                     You can now use  --port 0  to listen on an available port \n                 \n                 \n                     New  template_debug  setting for debugging templates, e.g.  https://latest.datasette.io/fixtures/roadside_attractions?_context=1  ( #654 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/636\", \"label\": \"#636\"}, {\"href\": \"https://github.com/simonw/datasette/issues/638\", \"label\": \"#638\"}, {\"href\": \"https://github.com/simonw/datasette/issues/637\", \"label\": \"#637\"}, {\"href\": \"https://github.com/simonw/datasette/issues/641\", \"label\": \"#641\"}, {\"href\": \"https://latest.datasette.io/fixtures/roadside_attractions?_context=1\", \"label\": \"https://latest.datasette.io/fixtures/roadside_attractions?_context=1\"}, {\"href\": \"https://github.com/simonw/datasette/issues/654\", \"label\": \"#654\"}]"}
{"id": "changelog:id71", "page": "changelog", "ref": "id71", "title": "0.32 (2019-11-14)", "content": "Datasette now renders templates using  Jinja async mode . This means plugins can provide custom template functions that perform asynchronous actions, for example the new  datasette-template-sql  plugin which allows custom templates to directly execute SQL queries and render their results. ( #628 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://jinja.palletsprojects.com/en/2.10.x/api/#async-support\", \"label\": \"Jinja async mode\"}, {\"href\": \"https://github.com/simonw/datasette-template-sql\", \"label\": \"datasette-template-sql\"}, {\"href\": \"https://github.com/simonw/datasette/issues/628\", \"label\": \"#628\"}]"}
{"id": "changelog:id72", "page": "changelog", "ref": "id72", "title": "0.31.2 (2019-11-13)", "content": "Fixed a bug where  datasette publish heroku  applications failed to start ( #633 ) \n                 \n                 \n                     Fix for  datasette publish  with just  --source_url  - thanks, Stanley Zheng ( #572 ) \n                 \n                 \n                     Deployments to Heroku now use Python 3.8.0 ( #632 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/633\", \"label\": \"#633\"}, {\"href\": \"https://github.com/simonw/datasette/issues/572\", \"label\": \"#572\"}, {\"href\": \"https://github.com/simonw/datasette/issues/632\", \"label\": \"#632\"}]"}
{"id": "changelog:id73", "page": "changelog", "ref": "id73", "title": "0.31.1 (2019-11-12)", "content": "Deployments created using  datasette publish   now use  python:3.8  base Docker image ( #629 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/pull/629\", \"label\": \"#629\"}]"}
{"id": "changelog:id74", "page": "changelog", "ref": "id74", "title": "0.31 (2019-11-11)", "content": "This version adds compatibility with Python 3.8 and breaks compatibility with Python 3.5. \n             If you are still running Python 3.5 you should stick with  0.30.2 , which you can install like this: \n             pip install datasette==0.30.2 \n             \n                 \n                     Format SQL button now works with read-only SQL queries - thanks, Tobias Kunze ( #602 ) \n                 \n                 \n                     New  ?column__notin=x,y,z  filter for table views ( #614 ) \n                 \n                 \n                     Table view now uses  select col1, col2, col3  instead of  select * \n                 \n                 \n                     Database filenames can now contain spaces - thanks, Tobias Kunze ( #590 ) \n                 \n                 \n                     Removed obsolete  ?_group_count=col  feature ( #504 ) \n                 \n                 \n                     Improved user interface and documentation for  datasette publish cloudrun  ( #608 ) \n                 \n                 \n                     Tables with indexes now show the  CREATE INDEX  statements on the table page ( #618 ) \n                 \n                 \n                     Current version of  uvicorn  is now shown on  /-/versions \n                 \n                 \n                     Python 3.8 is now supported! ( #622 ) \n                 \n                 \n                     Python 3.5 is no longer supported.", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/pull/602\", \"label\": \"#602\"}, {\"href\": \"https://github.com/simonw/datasette/issues/614\", \"label\": \"#614\"}, {\"href\": \"https://github.com/simonw/datasette/pull/590\", \"label\": \"#590\"}, {\"href\": \"https://github.com/simonw/datasette/issues/504\", \"label\": \"#504\"}, {\"href\": \"https://github.com/simonw/datasette/issues/608\", \"label\": \"#608\"}, {\"href\": \"https://github.com/simonw/datasette/issues/618\", \"label\": \"#618\"}, {\"href\": \"https://www.uvicorn.org/\", \"label\": \"uvicorn\"}, {\"href\": \"https://github.com/simonw/datasette/issues/622\", \"label\": \"#622\"}]"}
{"id": "changelog:id75", "page": "changelog", "ref": "id75", "title": "0.30.2 (2019-11-02)", "content": "/-/plugins  page now uses distribution name e.g.  datasette-cluster-map  instead of the name of the underlying Python package ( datasette_cluster_map ) ( #606 ) \n                 \n                 \n                     Array faceting is now only suggested for columns that contain arrays of strings ( #562 ) \n                 \n                 \n                     Better documentation for the  --host  argument ( #574 ) \n                 \n                 \n                     Don't show  None  with a broken link for the label on a nullable foreign key ( #406 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/606\", \"label\": \"#606\"}, {\"href\": \"https://github.com/simonw/datasette/issues/562\", \"label\": \"#562\"}, {\"href\": \"https://github.com/simonw/datasette/issues/574\", \"label\": \"#574\"}, {\"href\": \"https://github.com/simonw/datasette/issues/406\", \"label\": \"#406\"}]"}
{"id": "changelog:id76", "page": "changelog", "ref": "id76", "title": "0.30.1 (2019-10-30)", "content": "Fixed bug where  ?_where=  parameter was not persisted in hidden form fields ( #604 ) \n                 \n                 \n                     Fixed bug with .JSON representation of row pages - thanks, Chris Shaw ( #603 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/604\", \"label\": \"#604\"}, {\"href\": \"https://github.com/simonw/datasette/issues/603\", \"label\": \"#603\"}]"}
{"id": "changelog:id77", "page": "changelog", "ref": "id77", "title": "0.30 (2019-10-18)", "content": "Added  /-/threads  debugging page \n                 \n                 \n                     Allow  EXPLAIN WITH...  ( #583 ) \n                 \n                 \n                     Button to format SQL - thanks, Tobias Kunze ( #136 ) \n                 \n                 \n                     Sort databases on homepage by argument order - thanks, Tobias Kunze ( #585 ) \n                 \n                 \n                     Display metadata footer on custom SQL queries - thanks, Tobias Kunze ( #589 ) \n                 \n                 \n                     Use  --platform=managed  for  publish cloudrun  ( #587 ) \n                 \n                 \n                     Fixed bug returning non-ASCII characters in CSV ( #584 ) \n                 \n                 \n                     Fix for  /foo  v.s.  /foo-bar  bug ( #601 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/583\", \"label\": \"#583\"}, {\"href\": \"https://github.com/simonw/datasette/issues/136\", \"label\": \"#136\"}, {\"href\": \"https://github.com/simonw/datasette/issues/585\", \"label\": \"#585\"}, {\"href\": \"https://github.com/simonw/datasette/pull/589\", \"label\": \"#589\"}, {\"href\": \"https://github.com/simonw/datasette/issues/587\", \"label\": \"#587\"}, {\"href\": \"https://github.com/simonw/datasette/issues/584\", \"label\": \"#584\"}, {\"href\": \"https://github.com/simonw/datasette/issues/601\", \"label\": \"#601\"}]"}
{"id": "changelog:id78", "page": "changelog", "ref": "id78", "title": "0.29.3 (2019-09-02)", "content": "Fixed implementation of CodeMirror on database page ( #560 ) \n                 \n                 \n                     Documentation typo fixes - thanks, Min ho Kim ( #561 ) \n                 \n                 \n                     Mechanism for detecting if a table has FTS enabled now works if the table name used alternative escaping mechanisms ( #570 ) - for compatibility with  a recent change to sqlite-utils .", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/560\", \"label\": \"#560\"}, {\"href\": \"https://github.com/simonw/datasette/pull/561\", \"label\": \"#561\"}, {\"href\": \"https://github.com/simonw/datasette/issues/570\", \"label\": \"#570\"}, {\"href\": \"https://github.com/simonw/sqlite-utils/pull/57\", \"label\": \"a recent change to sqlite-utils\"}]"}
{"id": "changelog:id79", "page": "changelog", "ref": "id79", "title": "0.29.2 (2019-07-13)", "content": "Bumped  Uvicorn  to 0.8.4, fixing a bug where the query string was not included in the server logs. ( #559 ) \n                 \n                 \n                     Fixed bug where the navigation breadcrumbs were not displayed correctly on the page for a custom query. ( #558 ) \n                 \n                 \n                     Fixed bug where custom query names containing unicode characters caused errors.", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://www.uvicorn.org/\", \"label\": \"Uvicorn\"}, {\"href\": \"https://github.com/simonw/datasette/issues/559\", \"label\": \"#559\"}, {\"href\": \"https://github.com/simonw/datasette/issues/558\", \"label\": \"#558\"}]"}
{"id": "changelog:id8", "page": "changelog", "ref": "id8", "title": "0.64 (2023-01-09)", "content": "Datasette now  strongly recommends against allowing arbitrary SQL queries if you are using SpatiaLite . SpatiaLite includes SQL functions that could cause the Datasette server to crash. See  SpatiaLite  for more details. \n                 \n                 \n                     New  default_allow_sql  setting, providing an easier way to disable all arbitrary SQL execution by end users:  datasette --setting default_allow_sql off . See also  Controlling the ability to execute arbitrary SQL . ( #1409 ) \n                 \n                 \n                     Building a location to time zone API with SpatiaLite  is a new Datasette tutorial showing how to safely use SpatiaLite to create a location to time zone API. \n                 \n                 \n                     New documentation about  how to debug problems loading SQLite extensions . The error message shown when an extension cannot be loaded has also been improved. ( #1979 ) \n                 \n                 \n                     Fixed an accessibility issue: the  <select>  elements in the table filter form now show an outline when they are currently focused. ( #1771 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1409\", \"label\": \"#1409\"}, {\"href\": \"https://datasette.io/tutorials/spatialite\", \"label\": \"Building a location to time zone API with SpatiaLite\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1979\", \"label\": \"#1979\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1771\", \"label\": \"#1771\"}]"}
{"id": "changelog:id80", "page": "changelog", "ref": "id80", "title": "0.29.1 (2019-07-11)", "content": "Fixed bug with static mounts using relative paths which could lead to traversal exploits ( #555 ) - thanks Abdussamet Kocak! \n                 \n                 \n                     Datasette can now be run as a module:  python -m datasette  ( #556 ) - thanks, Abdussamet Kocak!", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/555\", \"label\": \"#555\"}, {\"href\": \"https://github.com/simonw/datasette/issues/556\", \"label\": \"#556\"}]"}
{"id": "changelog:id81", "page": "changelog", "ref": "id81", "title": "0.29 (2019-07-07)", "content": "ASGI, new plugin hooks, facet by date and much, much more...", "breadcrumbs": "[\"Changelog\"]", "references": "[]"}
{"id": "changelog:id82", "page": "changelog", "ref": "id82", "title": "0.28 (2019-05-19)", "content": "A  salmagundi  of new features!", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://adamj.eu/tech/2019/01/18/a-salmagundi-of-django-alpha-announcements/\", \"label\": \"salmagundi\"}]"}
{"id": "changelog:id83", "page": "changelog", "ref": "id83", "title": "Small changes", "content": "We now show the size of the database file next to the download link ( #172 ) \n                     \n                     \n                         New  /-/databases  introspection page shows currently connected databases ( #470 ) \n                     \n                     \n                         Binary data is no longer displayed on the table and row pages ( #442  - thanks, Russ Garrett) \n                     \n                     \n                         New show/hide SQL links on custom query pages ( #415 ) \n                     \n                     \n                         The  extra_body_script  plugin hook now accepts an optional  view_name  argument ( #443  - thanks, Russ Garrett) \n                     \n                     \n                         Bumped Jinja2 dependency to 2.10.1 ( #426 ) \n                     \n                     \n                         All table filters are now documented, and documentation is enforced via unit tests ( 2c19a27 ) \n                     \n                     \n                         New project guideline: master should stay shippable at all times! ( 31f36e1 ) \n                     \n                     \n                         Fixed a bug where  sqlite_timelimit()  occasionally failed to clean up after itself ( bac4e01 ) \n                     \n                     \n                         We no longer load additional plugins when executing pytest ( #438 ) \n                     \n                     \n                         Homepage now links to database views if there are less than five tables in a database ( #373 ) \n                     \n                     \n                         The  --cors  option is now respected by error pages ( #453 ) \n                     \n                     \n                         datasette publish heroku  now uses the  --include-vcs-ignore  option, which means it works under Travis CI ( #407 ) \n                     \n                     \n                         datasette publish heroku  now publishes using Python 3.6.8 ( 666c374 ) \n                     \n                     \n                         Renamed  datasette publish now  to  datasette publish nowv1  ( #472 ) \n                     \n                     \n                         datasette publish nowv1  now accepts multiple  --alias  parameters ( 09ef305 ) \n                     \n                     \n                         Removed the  datasette skeleton  command ( #476 ) \n                     \n                     \n                         The  documentation on how to build the documentation  now recommends  sphinx-autobuild", "breadcrumbs": "[\"Changelog\", \"0.28 (2019-05-19)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/172\", \"label\": \"#172\"}, {\"href\": \"https://github.com/simonw/datasette/issues/470\", \"label\": \"#470\"}, {\"href\": \"https://github.com/simonw/datasette/pull/442\", \"label\": \"#442\"}, {\"href\": \"https://github.com/simonw/datasette/issues/415\", \"label\": \"#415\"}, {\"href\": \"https://github.com/simonw/datasette/pull/443\", \"label\": \"#443\"}, {\"href\": \"https://github.com/simonw/datasette/pull/426\", \"label\": \"#426\"}, {\"href\": \"https://github.com/simonw/datasette/commit/2c19a27d15a913e5f3dd443f04067169a6f24634\", \"label\": \"2c19a27\"}, {\"href\": \"https://github.com/simonw/datasette/commit/31f36e1b97ccc3f4387c80698d018a69798b6228\", \"label\": \"31f36e1\"}, {\"href\": \"https://github.com/simonw/datasette/commit/bac4e01f40ae7bd19d1eab1fb9349452c18de8f5\", \"label\": \"bac4e01\"}, {\"href\": \"https://github.com/simonw/datasette/issues/438\", \"label\": \"#438\"}, {\"href\": \"https://github.com/simonw/datasette/issues/373\", \"label\": \"#373\"}, {\"href\": \"https://github.com/simonw/datasette/issues/453\", \"label\": \"#453\"}, {\"href\": \"https://github.com/simonw/datasette/pull/407\", \"label\": \"#407\"}, {\"href\": \"https://github.com/simonw/datasette/commit/666c37415a898949fae0437099d62a35b1e9c430\", \"label\": \"666c374\"}, {\"href\": \"https://github.com/simonw/datasette/issues/472\", \"label\": \"#472\"}, {\"href\": \"https://github.com/simonw/datasette/commit/09ef305c687399384fe38487c075e8669682deb4\", \"label\": \"09ef305\"}, {\"href\": \"https://github.com/simonw/datasette/issues/476\", \"label\": \"#476\"}]"}
{"id": "changelog:id84", "page": "changelog", "ref": "id84", "title": "0.27.1 (2019-05-09)", "content": "Tiny bugfix release: don't install  tests/  in the wrong place. Thanks, Veit Heller.", "breadcrumbs": "[\"Changelog\"]", "references": "[]"}
{"id": "changelog:id85", "page": "changelog", "ref": "id85", "title": "0.27 (2019-01-31)", "content": "New command:  datasette plugins  ( documentation ) shows you the currently installed list of plugins. \n                 \n                 \n                     Datasette can now output  newline-delimited JSON  using the new  ?_shape=array&_nl=on  query string option. \n                 \n                 \n                     Added documentation on  The Datasette Ecosystem . \n                 \n                 \n                     Now using Python 3.7.2 as the base for the official  Datasette Docker image .", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"http://ndjson.org/\", \"label\": \"newline-delimited JSON\"}, {\"href\": \"https://hub.docker.com/r/datasetteproject/datasette/\", \"label\": \"Datasette Docker image\"}]"}
{"id": "changelog:id86", "page": "changelog", "ref": "id86", "title": "0.26.1 (2019-01-10)", "content": "/-/versions  now includes SQLite  compile_options  ( #396 ) \n                 \n                 \n                     datasetteproject/datasette  Docker image now uses SQLite 3.26.0 ( #397 ) \n                 \n                 \n                     Cleaned up some deprecation warnings under Python 3.7", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/396\", \"label\": \"#396\"}, {\"href\": \"https://hub.docker.com/r/datasetteproject/datasette\", \"label\": \"datasetteproject/datasette\"}, {\"href\": \"https://github.com/simonw/datasette/issues/397\", \"label\": \"#397\"}]"}
{"id": "changelog:id87", "page": "changelog", "ref": "id87", "title": "0.26 (2019-01-02)", "content": "datasette serve --reload  now restarts Datasette if a database file changes on disk. \n                 \n                 \n                     datasette publish now  now takes an optional  --alias mysite.now.sh  argument. This will attempt to set an alias after the deploy completes. \n                 \n                 \n                     Fixed a bug where the advanced CSV export form failed to include the currently selected filters ( #393 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/393\", \"label\": \"#393\"}]"}
{"id": "changelog:id88", "page": "changelog", "ref": "id88", "title": "0.25.2 (2018-12-16)", "content": "datasette publish heroku  now uses the  python-3.6.7  runtime \n                 \n                 \n                     Added documentation on  how to build the documentation \n                 \n                 \n                     Added documentation covering  our release process \n                 \n                 \n                     Upgraded to pytest 4.0.2", "breadcrumbs": "[\"Changelog\"]", "references": "[]"}
{"id": "changelog:id89", "page": "changelog", "ref": "id89", "title": "0.25.1 (2018-11-04)", "content": "Documentation improvements plus a fix for publishing to Zeit Now. \n             \n                 \n                     datasette publish now  now uses Zeit's v1 platform, to work around the new 100MB image limit. Thanks, @slygent - closes  #366 .", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/366\", \"label\": \"#366\"}]"}
{"id": "changelog:id9", "page": "changelog", "ref": "id9", "title": "0.63.3 (2022-12-17)", "content": "Fixed a bug where  datasette --root , when running in Docker, would only output the URL to sign in as root when the server shut down, not when it started up. ( #1958 ) \n                 \n                 \n                     You no longer need to ensure  await datasette.invoke_startup()  has been called in order for Datasette to start correctly serving requests - this is now handled automatically the first time the server receives a request. This fixes a bug experienced when Datasette is served directly by an ASGI application server such as Uvicorn or Gunicorn. It also fixes a bug with the  datasette-gunicorn  plugin. ( #1955 )", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1958\", \"label\": \"#1958\"}, {\"href\": \"https://datasette.io/plugins/datasette-gunicorn\", \"label\": \"datasette-gunicorn\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1955\", \"label\": \"#1955\"}]"}
{"id": "changelog:id90", "page": "changelog", "ref": "id90", "title": "0.25 (2018-09-19)", "content": "New plugin hooks, improved database view support and an easier way to use more recent versions of SQLite. \n             \n                 \n                     New  publish_subcommand  plugin hook. A plugin can now add additional  datasette publish  publishers in addition to the default  now  and  heroku , both of which have been refactored into default plugins.  publish_subcommand documentation . Closes  #349 \n                 \n                 \n                     New  render_cell  plugin hook. Plugins can now customize how values are displayed in the HTML tables produced by Datasette's browsable interface.  datasette-json-html  and  datasette-render-images  are two new plugins that use this hook.  render_cell documentation . Closes  #352 \n                 \n                 \n                     New  extra_body_script  plugin hook, enabling plugins to provide additional JavaScript that should be added to the page footer.  extra_body_script documentation . \n                 \n                 \n                     extra_css_urls  and  extra_js_urls  hooks now take additional optional parameters, allowing them to be more selective about which pages they apply to.  Documentation . \n                 \n                 \n                     You can now use the  sortable_columns metadata setting  to explicitly enable sort-by-column in the interface for database views, as well as for specific tables. \n                 \n                 \n                     The new  fts_table  and  fts_pk  metadata settings can now be used to  explicitly configure full-text search for a table or a view , even if that table is not directly coupled to the SQLite FTS feature in the database schema itself. \n                 \n                 \n                     Datasette will now use  pysqlite3  in place of the standard library  sqlite3  module if it has been installed in the current environment. This makes it much easier to run Datasette against a more recent version of SQLite, including the just-released  SQLite 3.25.0  which adds window function support. More details on how to use this in  #360 \n                 \n                 \n                     New mechanism that allows  plugin configuration options  to be set using  metadata.json .", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/349\", \"label\": \"#349\"}, {\"href\": \"https://github.com/simonw/datasette-json-html\", \"label\": \"datasette-json-html\"}, {\"href\": \"https://github.com/simonw/datasette-render-images\", \"label\": \"datasette-render-images\"}, {\"href\": \"https://github.com/simonw/datasette/issues/352\", \"label\": \"#352\"}, {\"href\": \"https://github.com/coleifer/pysqlite3\", \"label\": \"pysqlite3\"}, {\"href\": \"https://www.sqlite.org/releaselog/3_25_0.html\", \"label\": \"SQLite 3.25.0\"}, {\"href\": \"https://github.com/simonw/datasette/issues/360\", \"label\": \"#360\"}]"}
{"id": "changelog:id91", "page": "changelog", "ref": "id91", "title": "0.24 (2018-07-23)", "content": "A number of small new features: \n             \n                 \n                     datasette publish heroku  now supports  --extra-options , fixes  #334 \n                 \n                 \n                     Custom error message if SpatiaLite is needed for specified database, closes  #331 \n                 \n                 \n                     New config option:  truncate_cells_html  for  truncating long cell values  in HTML view - closes  #330 \n                 \n                 \n                     Documentation for  datasette publish and datasette package , closes  #337 \n                 \n                 \n                     Fixed compatibility with Python 3.7 \n                 \n                 \n                     datasette publish heroku  now supports app names via the  -n  option, which can also be used to overwrite an existing application [Russ Garrett] \n                 \n                 \n                     Title and description metadata can now be set for  canned SQL queries , closes  #342 \n                 \n                 \n                     New  force_https_on  config option, fixes  https://  API URLs when deploying to Zeit Now - closes  #333 \n                 \n                 \n                     ?_json_infinity=1  query string argument for handling Infinity/-Infinity values in JSON, closes  #332 \n                 \n                 \n                     URLs displayed in the results of custom SQL queries are now URLified, closes  #298", "breadcrumbs": "[\"Changelog\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/334\", \"label\": \"#334\"}, {\"href\": \"https://github.com/simonw/datasette/issues/331\", \"label\": \"#331\"}, {\"href\": \"https://github.com/simonw/datasette/issues/330\", \"label\": \"#330\"}, {\"href\": \"https://github.com/simonw/datasette/issues/337\", \"label\": \"#337\"}, {\"href\": \"https://github.com/simonw/datasette/issues/342\", \"label\": \"#342\"}, {\"href\": \"https://github.com/simonw/datasette/issues/333\", \"label\": \"#333\"}, {\"href\": \"https://github.com/simonw/datasette/issues/332\", \"label\": \"#332\"}, {\"href\": \"https://github.com/simonw/datasette/issues/298\", \"label\": \"#298\"}]"}
{"id": "changelog:improved-support-for-spatialite", "page": "changelog", "ref": "improved-support-for-spatialite", "title": "Improved support for SpatiaLite", "content": "The  SpatiaLite module \n                    for SQLite adds robust geospatial features to the database. \n                 Getting SpatiaLite working can be tricky, especially if you want to use the most\n                    recent alpha version (with support for K-nearest neighbor). \n                 Datasette now includes  extensive documentation on SpatiaLite , and thanks to  Ravi Kotecha  our GitHub\n                    repo includes a  Dockerfile  that can build\n                    the latest SpatiaLite and configure it for use with Datasette. \n                 The  datasette publish  and  datasette package  commands now accept a new\n                     --spatialite  argument which causes them to install and configure SpatiaLite\n                    as part of the container they deploy.", "breadcrumbs": "[\"Changelog\", \"0.23 (2018-06-18)\"]", "references": "[{\"href\": \"https://www.gaia-gis.it/fossil/libspatialite/index\", \"label\": \"SpatiaLite module\"}, {\"href\": \"https://github.com/r4vi\", \"label\": \"Ravi Kotecha\"}, {\"href\": \"https://github.com/simonw/datasette/blob/master/Dockerfile\", \"label\": \"Dockerfile\"}]"}
{"id": "changelog:javascript-modules", "page": "changelog", "ref": "javascript-modules", "title": "JavaScript modules", "content": "JavaScript modules  were introduced in ECMAScript 2015 and provide native browser support for the  import  and  export  keywords. \n                 To use modules, JavaScript needs to be included in  <script>  tags with a  type=\"module\"  attribute. \n                 Datasette now has the ability to output  <script type=\"module\">  in places where you may wish to take advantage of modules. The  extra_js_urls  option described in  Custom CSS and JavaScript  can now be used with modules, and module support is also available for the  extra_body_script()  plugin hook. ( #1186 ,  #1187 ) \n                 datasette-leaflet-freedraw  is the first example of a Datasette plugin that takes advantage of the new support for JavaScript modules. See  Drawing shapes on a map to query a SpatiaLite database  for more on this plugin.", "breadcrumbs": "[\"Changelog\", \"0.54 (2021-01-25)\"]", "references": "[{\"href\": \"https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules\", \"label\": \"JavaScript modules\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1186\", \"label\": \"#1186\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1187\", \"label\": \"#1187\"}, {\"href\": \"https://datasette.io/plugins/datasette-leaflet-freedraw\", \"label\": \"datasette-leaflet-freedraw\"}, {\"href\": \"https://simonwillison.net/2021/Jan/24/drawing-shapes-spatialite/\", \"label\": \"Drawing shapes on a map to query a SpatiaLite database\"}]"}
{"id": "changelog:latest-datasette-io", "page": "changelog", "ref": "latest-datasette-io", "title": "latest.datasette.io", "content": "Every commit to Datasette master is now automatically deployed by Travis CI to\n                     https://latest.datasette.io/  - ensuring there is always a live demo of the\n                    latest version of the software. \n                 The demo uses  the fixtures  from our\n                    unit tests, ensuring it demonstrates the same range of functionality that is\n                    covered by the tests. \n                 You can see how the deployment mechanism works in our  .travis.yml  file.", "breadcrumbs": "[\"Changelog\", \"0.23 (2018-06-18)\"]", "references": "[{\"href\": \"https://latest.datasette.io/\", \"label\": \"https://latest.datasette.io/\"}, {\"href\": \"https://github.com/simonw/datasette/blob/master/tests/fixtures.py\", \"label\": \"the fixtures\"}, {\"href\": \"https://github.com/simonw/datasette/blob/master/.travis.yml\", \"label\": \".travis.yml\"}]"}
{"id": "changelog:log-out", "page": "changelog", "ref": "log-out", "title": "Log out", "content": "The  ds_actor cookie  can be used by plugins (or by Datasette's  --root mechanism ) to authenticate users. The new  /-/logout  page provides a way to clear that cookie. \n                 A \"Log out\" button now shows in the global navigation provided the user is authenticated using the  ds_actor  cookie. ( #840 )", "breadcrumbs": "[\"Changelog\", \"0.45 (2020-07-01)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/840\", \"label\": \"#840\"}]"}
{"id": "changelog:magic-parameters-for-canned-queries", "page": "changelog", "ref": "magic-parameters-for-canned-queries", "title": "Magic parameters for canned queries", "content": "Canned queries now support  Magic parameters , which can be used to insert or select automatically generated values. For example: \n                 insert into logs\n  (user_id, timestamp)\nvalues\n  (:_actor_id, :_now_datetime_utc) \n                 This inserts the currently authenticated actor ID and the current datetime. ( #842 )", "breadcrumbs": "[\"Changelog\", \"0.45 (2020-07-01)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/842\", \"label\": \"#842\"}]"}
{"id": "changelog:miscellaneous", "page": "changelog", "ref": "miscellaneous", "title": "Miscellaneous", "content": "Got JSON data in one of your columns? Use the new  ?_json=COLNAME  argument\n                            to tell Datasette to return that JSON value directly rather than encoding it\n                            as a string. \n                     \n                     \n                         If you just want an array of the first value of each row, use the new\n                             ?_shape=arrayfirst  option -  example .", "breadcrumbs": "[\"Changelog\", \"0.23 (2018-06-18)\"]", "references": "[{\"href\": \"https://latest.datasette.io/fixtures.json?sql=select+neighborhood+from+facetable+order+by+pk+limit+101&_shape=arrayfirst\", \"label\": \"example\"}]"}
{"id": "changelog:named-in-memory-database-support", "page": "changelog", "ref": "named-in-memory-database-support", "title": "Named in-memory database support", "content": "As part of the work building the  _internal  database, Datasette now supports named in-memory databases that can be shared across multiple connections. This allows plugins to create in-memory databases which will persist data for the lifetime of the Datasette server process. ( #1151 ) \n                 The new  memory_name=  parameter to the  Database class  can be used to create named, shared in-memory databases.", "breadcrumbs": "[\"Changelog\", \"0.54 (2021-01-25)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1151\", \"label\": \"#1151\"}]"}
{"id": "changelog:new-configuration-settings", "page": "changelog", "ref": "new-configuration-settings", "title": "New configuration settings", "content": "Datasette's  Settings  now also supports boolean settings. A number of new\n                    configuration options have been added: \n                 \n                     \n                         num_sql_threads  - the number of threads used to execute SQLite queries. Defaults to 3. \n                     \n                     \n                         allow_facet  - enable or disable custom  Facets  using the  _facet=  parameter. Defaults to on. \n                     \n                     \n                         suggest_facets  - should Datasette suggest facets? Defaults to on. \n                     \n                     \n                         allow_download  - should users be allowed to download the entire SQLite database? Defaults to on. \n                     \n                     \n                         allow_sql  - should users be allowed to execute custom SQL queries? Defaults to on. \n                     \n                     \n                         default_cache_ttl  - Default HTTP caching max-age header in seconds. Defaults to 365 days - caching can be disabled entirely by settings this to 0. \n                     \n                     \n                         cache_size_kb  - Set the amount of memory SQLite uses for its  per-connection cache , in KB. \n                     \n                     \n                         allow_csv_stream  - allow users to stream entire result sets as a single CSV file. Defaults to on. \n                     \n                     \n                         max_csv_mb  - maximum size of a returned CSV file in MB. Defaults to 100MB, set to 0 to disable this limit.", "breadcrumbs": "[\"Changelog\", \"0.23 (2018-06-18)\"]", "references": "[{\"href\": \"https://www.sqlite.org/pragma.html#pragma_cache_size\", \"label\": \"per-connection cache\"}]"}
{"id": "changelog:new-features", "page": "changelog", "ref": "new-features", "title": "New features", "content": "If an error occurs while executing a user-provided SQL query, that query is now re-displayed in an editable form along with the error message. ( #619 ) \n                     \n                     \n                         New  ?_col=  and  ?_nocol=  parameters to show and hide columns in a table, plus an interface for hiding and showing columns in the column cog menu. ( #615 ) \n                     \n                     \n                         A new  ?_facet_size=  parameter for customizing the number of facet results returned on a table or view page. ( #1332 ) \n                     \n                     \n                         ?_facet_size=max  sets that to the maximum, which defaults to 1,000 and is controlled by the the  max_returned_rows  setting. If facet results are truncated the \u2026 at the bottom of the facet list now links to this parameter. ( #1337 ) \n                     \n                     \n                         ?_nofacet=1  option to disable all facet calculations on a page, used as a performance optimization for CSV exports and  ?_shape=array/object . ( #1349 ,  #263 ) \n                     \n                     \n                         ?_nocount=1  option to disable full query result counts. ( #1353 ) \n                     \n                     \n                         ?_trace=1  debugging option is now controlled by the new  trace_debug  setting, which is turned off by default. ( #1359 )", "breadcrumbs": "[\"Changelog\", \"0.57 (2021-06-05)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/619\", \"label\": \"#619\"}, {\"href\": \"https://github.com/simonw/datasette/issues/615\", \"label\": \"#615\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1332\", \"label\": \"#1332\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1337\", \"label\": \"#1337\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1349\", \"label\": \"#1349\"}, {\"href\": \"https://github.com/simonw/datasette/issues/263\", \"label\": \"#263\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1353\", \"label\": \"#1353\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1359\", \"label\": \"#1359\"}]"}
{"id": "changelog:new-plugin-hook-asgi-wrapper", "page": "changelog", "ref": "new-plugin-hook-asgi-wrapper", "title": "New plugin hook: asgi_wrapper", "content": "The  asgi_wrapper(datasette)  plugin hook allows plugins to entirely wrap the Datasette ASGI application in their own ASGI middleware. ( #520 ) \n                 Two new plugins take advantage of this hook: \n                 \n                     \n                         datasette-auth-github  adds a authentication layer: users will have to sign in using their GitHub account before they can view data or interact with Datasette. You can also use it to restrict access to specific GitHub users, or to members of specified GitHub  organizations  or  teams . \n                     \n                     \n                         datasette-cors  allows you to configure  CORS headers  for your Datasette instance. You can use this to enable JavaScript running on a whitelisted set of domains to make  fetch()  calls to the JSON API provided by your Datasette instance.", "breadcrumbs": "[\"Changelog\", \"0.29 (2019-07-07)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/520\", \"label\": \"#520\"}, {\"href\": \"https://github.com/simonw/datasette-auth-github\", \"label\": \"datasette-auth-github\"}, {\"href\": \"https://help.github.com/en/articles/about-organizations\", \"label\": \"organizations\"}, {\"href\": \"https://help.github.com/en/articles/organizing-members-into-teams\", \"label\": \"teams\"}, {\"href\": \"https://github.com/simonw/datasette-cors\", \"label\": \"datasette-cors\"}, {\"href\": \"https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS\", \"label\": \"CORS headers\"}]"}
{"id": "changelog:new-plugin-hook-extra-template-vars", "page": "changelog", "ref": "new-plugin-hook-extra-template-vars", "title": "New plugin hook: extra_template_vars", "content": "The  extra_template_vars(template, database, table, columns, view_name, request, datasette)  plugin hook allows plugins to inject their own additional variables into the Datasette template context. This can be used in conjunction with custom templates to customize the Datasette interface.  datasette-auth-github  uses this hook to add custom HTML to the new top navigation bar (which is designed to be modified by plugins, see  #540 ).", "breadcrumbs": "[\"Changelog\", \"0.29 (2019-07-07)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette-auth-github\", \"label\": \"datasette-auth-github\"}, {\"href\": \"https://github.com/simonw/datasette/issues/540\", \"label\": \"#540\"}]"}
{"id": "changelog:new-plugin-hooks", "page": "changelog", "ref": "new-plugin-hooks", "title": "New plugin hooks", "content": "register_magic_parameters(datasette)  can be used to define new types of magic canned query parameters. \n                     \n                     \n                         startup(datasette)  can run custom code when Datasette first starts up.  datasette-init  is a new plugin that uses this hook to create database tables and views on startup if they have not yet been created. ( #834 ) \n                     \n                     \n                         canned_queries(datasette, database, actor)  lets plugins provide additional canned queries beyond those defined in Datasette's metadata. See  datasette-saved-queries  for an example of this hook in action. ( #852 ) \n                     \n                     \n                         forbidden(datasette, request, message)  is a hook for customizing how Datasette responds to 403 forbidden errors. ( #812 )", "breadcrumbs": "[\"Changelog\", \"0.45 (2020-07-01)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette-init\", \"label\": \"datasette-init\"}, {\"href\": \"https://github.com/simonw/datasette/issues/834\", \"label\": \"#834\"}, {\"href\": \"https://github.com/simonw/datasette-saved-queries\", \"label\": \"datasette-saved-queries\"}, {\"href\": \"https://github.com/simonw/datasette/issues/852\", \"label\": \"#852\"}, {\"href\": \"https://github.com/simonw/datasette/issues/812\", \"label\": \"#812\"}]"}
{"id": "changelog:new-visual-design", "page": "changelog", "ref": "new-visual-design", "title": "New visual design", "content": "Datasette is no longer white and grey with blue and purple links!  Natalie Downe  has been working on a visual refresh, the first iteration of which is included in this release. ( #1056 )", "breadcrumbs": "[\"Changelog\", \"0.51 (2020-10-31)\"]", "references": "[{\"href\": \"https://twitter.com/natbat\", \"label\": \"Natalie Downe\"}, {\"href\": \"https://github.com/simonw/datasette/pull/1056\", \"label\": \"#1056\"}]"}
{"id": "changelog:other-changes", "page": "changelog", "ref": "other-changes", "title": "Other changes", "content": "Datasette can now open multiple database files with the same name, e.g. if you run  datasette path/to/one.db path/to/other/one.db . ( #509 ) \n                     \n                     \n                         datasette publish cloudrun  now sets  force_https_urls  for every deployment, fixing some incorrect  http://  links. ( #1178 ) \n                     \n                     \n                         Fixed a bug in the example nginx configuration in  Running Datasette behind a proxy . ( #1091 ) \n                     \n                     \n                         The  Datasette Ecosystem  documentation page has been reduced in size in favour of the  datasette.io   tools  and  plugins  directories. ( #1182 ) \n                     \n                     \n                         The request object now provides a  request.full_path  property, which returns the path including any query string. ( #1184 ) \n                     \n                     \n                         Better error message for disallowed  PRAGMA  clauses in SQL queries. ( #1185 ) \n                     \n                     \n                         datasette publish heroku  now deploys using  python-3.8.7 . \n                     \n                     \n                         New plugin testing documentation on  Testing outbound HTTP calls with pytest-httpx . ( #1198 ) \n                     \n                     \n                         All  ?_*  query string parameters passed to the table page are now persisted in hidden form fields, so parameters such as  ?_size=10  will be correctly passed to the next page when query filters are changed. ( #1194 ) \n                     \n                     \n                         Fixed a bug loading a database file called  test-database (1).sqlite . ( #1181 )", "breadcrumbs": "[\"Changelog\", \"0.54 (2021-01-25)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/509\", \"label\": \"#509\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1178\", \"label\": \"#1178\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1091\", \"label\": \"#1091\"}, {\"href\": \"https://datasette.io/tools\", \"label\": \"tools\"}, {\"href\": \"https://datasette.io/plugins\", \"label\": \"plugins\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1182\", \"label\": \"#1182\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1184\", \"label\": \"#1184\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1185\", \"label\": \"#1185\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1198\", \"label\": \"#1198\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1194\", \"label\": \"#1194\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1181\", \"label\": \"#1181\"}]"}
{"id": "changelog:other-small-fixes", "page": "changelog", "ref": "other-small-fixes", "title": "Other small fixes", "content": "Made several performance improvements to the database schema introspection code that runs when Datasette first starts up. ( #1555 ) \n                     \n                     \n                         Label columns detected for foreign keys are now case-insensitive, so  Name  or  TITLE  will be detected in the same way as  name  or  title . ( #1544 ) \n                     \n                     \n                         Upgraded Pluggy dependency to 1.0. ( #1575 ) \n                     \n                     \n                         Now using  Plausible analytics  for the Datasette documentation. \n                     \n                     \n                         explain query plan  is now allowed with varying amounts of whitespace in the query. ( #1588 ) \n                     \n                     \n                         New  CLI reference  page showing the output of  --help  for each of the  datasette  sub-commands. This lead to several small improvements to the help copy. ( #1594 ) \n                     \n                     \n                         Fixed bug where writable canned queries could not be used with custom templates.  ( #1547 ) \n                     \n                     \n                         Improved fix for a bug where columns with a underscore prefix could result in unnecessary hidden form fields. ( #1527 )", "breadcrumbs": "[\"Changelog\", \"0.60 (2022-01-13)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1555\", \"label\": \"#1555\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1544\", \"label\": \"#1544\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1575\", \"label\": \"#1575\"}, {\"href\": \"https://plausible.io/\", \"label\": \"Plausible analytics\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1588\", \"label\": \"#1588\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1594\", \"label\": \"#1594\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1547\", \"label\": \"#1547\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1527\", \"label\": \"#1527\"}]"}
{"id": "changelog:permissions", "page": "changelog", "ref": "permissions", "title": "Permissions", "content": "Datasette also now has a built-in concept of  Permissions . The permissions system answers the following question: \n                 \n                     Is this  actor  allowed to perform this  action , optionally against this particular  resource ? \n                 \n                 You can use the new  \"allow\"  block syntax in  metadata.json  (or  metadata.yaml ) to set required permissions at the instance, database, table or canned query level. For example, to restrict access to the  fixtures.db  database to the  \"root\"  user: \n                 {\n    \"databases\": {\n        \"fixtures\": {\n            \"allow\": {\n                \"id\" \"root\"\n            }\n        }\n    }\n} \n                 See  Defining permissions with \"allow\" blocks  for more details. \n                 Plugins can implement their own custom permission checks using the new  permission_allowed(datasette, actor, action, resource)  hook. \n                 A new debug page at  /-/permissions  shows recent permission checks, to help administrators and plugin authors understand exactly what checks are being performed. This tool defaults to only being available to the root user, but can be exposed to other users by plugins that respond to the  permissions-debug  permission. ( #788 )", "breadcrumbs": "[\"Changelog\", \"0.44 (2020-06-11)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/788\", \"label\": \"#788\"}]"}
{"id": "changelog:plugin-hooks", "page": "changelog", "ref": "plugin-hooks", "title": "Plugin hooks", "content": "New plugin hook:  handle_exception() , for custom handling of exceptions caught by Datasette. ( #1770 ) \n                     \n                     \n                         The  render_cell()  plugin hook is now also passed a  row  argument, representing the  sqlite3.Row  object that is being rendered. ( #1300 ) \n                     \n                     \n                         The  configuration directory  is now stored in  datasette.config_dir , making it available to plugins. Thanks, Chris Amico. ( #1766 )", "breadcrumbs": "[\"Changelog\", \"0.62 (2022-08-14)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1770\", \"label\": \"#1770\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1300\", \"label\": \"#1300\"}, {\"href\": \"https://github.com/simonw/datasette/pull/1766\", \"label\": \"#1766\"}]"}
{"id": "changelog:plugin-hooks-and-internals", "page": "changelog", "ref": "plugin-hooks-and-internals", "title": "Plugin hooks and internals", "content": "The  prepare_jinja2_environment(env, datasette)  plugin hook now accepts an optional  datasette  argument. Hook implementations can also now return an  async  function which will be awaited automatically. ( #1809 ) \n                     \n                     \n                         Database(is_mutable=)  now defaults to  True . ( #1808 ) \n                     \n                     \n                         The  datasette.check_visibility()  method now accepts an optional  permissions=  list, allowing it to take multiple permissions into account at once when deciding if something should be shown as public or private. This has been used to correctly display padlock icons in more places in the Datasette interface. ( #1829 ) \n                     \n                     \n                         Datasette no longer enforces upper bounds on its dependencies. ( #1800 )", "breadcrumbs": "[\"Changelog\", \"0.63 (2022-10-27)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1809\", \"label\": \"#1809\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1808\", \"label\": \"#1808\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1829\", \"label\": \"#1829\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1800\", \"label\": \"#1800\"}]"}
{"id": "changelog:plugins-and-internals", "page": "changelog", "ref": "plugins-and-internals", "title": "Plugins and internals", "content": "New plugin hook:  filters_from_request(request, database, table, datasette) , which runs on the table page and can be used to support new custom query string parameters that modify the SQL query. ( #473 ) \n                     \n                     \n                         Added two additional methods for writing to the database:  await db.execute_write_script(sql, block=True)  and  await db.execute_write_many(sql, params_seq, block=True) . ( #1570 ) \n                     \n                     \n                         The  db.execute_write()  internal method now defaults to blocking until the write operation has completed. Previously it defaulted to queuing the write and then continuing to run code while the write was in the queue. ( #1579 ) \n                     \n                     \n                         Database write connections now execute the  prepare_connection(conn, database, datasette)  plugin hook. ( #1564 ) \n                     \n                     \n                         The  Datasette()  constructor no longer requires the  files=  argument, and is now documented at  Datasette class . ( #1563 ) \n                     \n                     \n                         The tracing feature now traces write queries, not just read queries. ( #1568 ) \n                     \n                     \n                         The query string variables exposed by  request.args  will now include blank strings for arguments such as  foo  in  ?foo=&bar=1  rather than ignoring those parameters entirely. ( #1551 )", "breadcrumbs": "[\"Changelog\", \"0.60 (2022-01-13)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/473\", \"label\": \"#473\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1570\", \"label\": \"#1570\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1579\", \"label\": \"#1579\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1564\", \"label\": \"#1564\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1563\", \"label\": \"#1563\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1568\", \"label\": \"#1568\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1551\", \"label\": \"#1551\"}]"}
{"id": "changelog:plugins-can-now-add-links-within-datasette", "page": "changelog", "ref": "plugins-can-now-add-links-within-datasette", "title": "Plugins can now add links within Datasette", "content": "A number of existing Datasette plugins add new pages to the Datasette interface, providig tools for things like  uploading CSVs ,  editing table schemas  or  configuring full-text search . \n                 Plugins like this can now link to themselves from other parts of Datasette interface. The  menu_links(datasette, actor, request)  hook ( #1064 ) lets plugins add links to Datasette's new top-right application menu, and the  table_actions(datasette, actor, database, table, request)  hook ( #1066 ) adds links to a new \"table actions\" menu on the table page. \n                 The demo at  latest.datasette.io  now includes some example plugins. To see the new table actions menu first  sign into that demo as root  and then visit the  facetable  table to see the new cog icon menu at the top of the page.", "breadcrumbs": "[\"Changelog\", \"0.51 (2020-10-31)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette-upload-csvs\", \"label\": \"uploading CSVs\"}, {\"href\": \"https://github.com/simonw/datasette-edit-schema\", \"label\": \"editing table schemas\"}, {\"href\": \"https://github.com/simonw/datasette-configure-fts\", \"label\": \"configuring full-text search\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1064\", \"label\": \"#1064\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1066\", \"label\": \"#1066\"}, {\"href\": \"https://latest.datasette.io/\", \"label\": \"latest.datasette.io\"}, {\"href\": \"https://latest.datasette.io/login-as-root\", \"label\": \"sign into that demo as root\"}, {\"href\": \"https://latest.datasette.io/fixtures/facetable\", \"label\": \"facetable\"}]"}
{"id": "changelog:register-routes-plugin-hooks", "page": "changelog", "ref": "register-routes-plugin-hooks", "title": "register_routes() plugin hooks", "content": "Plugins can now register new views and routes via the  register_routes(datasette)  plugin hook ( #819 ). View functions can be defined that accept any of the current  datasette  object, the current  request , or the ASGI  scope ,  send  and  receive  objects.", "breadcrumbs": "[\"Changelog\", \"0.44 (2020-06-11)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/819\", \"label\": \"#819\"}]"}
{"id": "changelog:running-datasette-behind-a-proxy", "page": "changelog", "ref": "running-datasette-behind-a-proxy", "title": "Running Datasette behind a proxy", "content": "The  base_url  configuration option is designed to help run Datasette on a specific path behind a proxy - for example if you want to run an instance of Datasette at  /my-datasette/  within your existing site's URL hierarchy, proxied behind nginx or Apache. \n                 Support for this configuration option has been greatly improved ( #1023 ), and guidelines for using it are now available in a new documentation section on  Running Datasette behind a proxy . ( #1027 )", "breadcrumbs": "[\"Changelog\", \"0.51 (2020-10-31)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/1023\", \"label\": \"#1023\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1027\", \"label\": \"#1027\"}]"}
{"id": "changelog:secret-plugin-configuration-options", "page": "changelog", "ref": "secret-plugin-configuration-options", "title": "Secret plugin configuration options", "content": "Plugins like  datasette-auth-github  need a safe way to set secret configuration options. Since the default mechanism for configuring plugins exposes those settings in  /-/metadata  a new mechanism was needed.  Secret configuration values  describes how plugins can now specify that their settings should be read from a file or an environment variable: \n                 {\n    \"plugins\": {\n        \"datasette-auth-github\": {\n            \"client_secret\": {\n                \"$env\": \"GITHUB_CLIENT_SECRET\"\n            }\n        }\n    }\n} \n                 These plugin secrets can be set directly using  datasette publish . See  Custom metadata and plugins  for details. ( #538  and  #543 )", "breadcrumbs": "[\"Changelog\", \"0.29 (2019-07-07)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette-auth-github\", \"label\": \"datasette-auth-github\"}, {\"href\": \"https://github.com/simonw/datasette/issues/538\", \"label\": \"#538\"}, {\"href\": \"https://github.com/simonw/datasette/issues/543\", \"label\": \"#543\"}]"}
{"id": "changelog:signed-values-and-secrets", "page": "changelog", "ref": "signed-values-and-secrets", "title": "Signed values and secrets", "content": "Both flash messages and user authentication needed a way to sign values and set signed cookies. Two new methods are now available for plugins to take advantage of this mechanism:  .sign(value, namespace=\"default\")  and  .unsign(value, namespace=\"default\") . \n                 Datasette will generate a secret automatically when it starts up, but to avoid resetting the secret (and hence invalidating any cookies) every time the server restarts you should set your own secret. You can pass a secret to Datasette using the new  --secret  option or with a  DATASETTE_SECRET  environment variable. See  Configuring the secret  for more details. \n                 You can also set a secret when you deploy Datasette using  datasette publish  or  datasette package  - see  Using secrets with datasette publish . \n                 Plugins can now sign values and verify their signatures using the  datasette.sign()  and  datasette.unsign()  methods.", "breadcrumbs": "[\"Changelog\", \"0.44 (2020-06-11)\"]", "references": "[]"}
{"id": "changelog:small-changes", "page": "changelog", "ref": "small-changes", "title": "Small changes", "content": "Databases published using  datasette publish  now open in  Immutable mode . ( #469 ) \n                     \n                     \n                         ?col__date=  now works for columns containing spaces \n                     \n                     \n                         Automatic label detection (for deciding which column to show when linking to a foreign key) has been improved. ( #485 ) \n                     \n                     \n                         Fixed bug where pagination broke when combined with an expanded foreign key. ( #489 ) \n                     \n                     \n                         Contributors can now run  pip install -e .[docs]  to get all of the dependencies needed to build the documentation, including  cd docs && make livehtml  support. \n                     \n                     \n                         Datasette's dependencies are now all specified using the  ~=  match operator. ( #532 ) \n                     \n                     \n                         white-space: pre-wrap  now used for table creation SQL. ( #505 ) \n                     \n                 \n                 Full list of commits  between 0.28 and 0.29.", "breadcrumbs": "[\"Changelog\", \"0.29 (2019-07-07)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/469\", \"label\": \"#469\"}, {\"href\": \"https://github.com/simonw/datasette/issues/485\", \"label\": \"#485\"}, {\"href\": \"https://github.com/simonw/datasette/issues/489\", \"label\": \"#489\"}, {\"href\": \"https://github.com/simonw/datasette/issues/532\", \"label\": \"#532\"}, {\"href\": \"https://github.com/simonw/datasette/issues/505\", \"label\": \"#505\"}, {\"href\": \"https://github.com/simonw/datasette/compare/0.28...0.29\", \"label\": \"Full list of commits\"}]"}
{"id": "changelog:smaller-changes", "page": "changelog", "ref": "smaller-changes", "title": "Smaller changes", "content": "Wide tables shown within Datasette now scroll horizontally ( #998 ). This is achieved using a new  <div class=\"table-wrapper\">  element which may impact the implementation of some plugins (for example  this change to datasette-cluster-map ). \n                     \n                     \n                         New  debug-menu  permission. ( #1068 ) \n                     \n                     \n                         Removed  --debug  option, which didn't do anything. ( #814 ) \n                     \n                     \n                         Link:  HTTP header pagination. ( #1014 ) \n                     \n                     \n                         x  button for clearing filters. ( #1016 ) \n                     \n                     \n                         Edit SQL button on canned queries, ( #1019 ) \n                     \n                     \n                         --load-extension=spatialite  shortcut. ( #1028 ) \n                     \n                     \n                         scale-in animation for column action menu. ( #1039 ) \n                     \n                     \n                         Option to pass a list of templates to  .render_template()  is now documented. ( #1045 ) \n                     \n                     \n                         New  datasette.urls.static_plugins()  method. ( #1033 ) \n                     \n                     \n                         datasette -o  option now opens the most relevant page. ( #976 ) \n                     \n                     \n                         datasette --cors  option now enables access to  /database.db  downloads. ( #1057 ) \n                     \n                     \n                         Database file downloads now implement cascading permissions, so you can download a database if you have  view-database-download  permission even if you do not have permission to access the Datasette instance. ( #1058 ) \n                     \n                     \n                         New documentation on  Designing URLs for your plugin . ( #1053 )", "breadcrumbs": "[\"Changelog\", \"0.51 (2020-10-31)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/998\", \"label\": \"#998\"}, {\"href\": \"https://github.com/simonw/datasette-cluster-map/commit/fcb4abbe7df9071c5ab57defd39147de7145b34e\", \"label\": \"this change to datasette-cluster-map\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1068\", \"label\": \"#1068\"}, {\"href\": \"https://github.com/simonw/datasette/issues/814\", \"label\": \"#814\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1014\", \"label\": \"#1014\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1016\", \"label\": \"#1016\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1019\", \"label\": \"#1019\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1028\", \"label\": \"#1028\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1039\", \"label\": \"#1039\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1045\", \"label\": \"#1045\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1033\", \"label\": \"#1033\"}, {\"href\": \"https://github.com/simonw/datasette/issues/976\", \"label\": \"#976\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1057\", \"label\": \"#1057\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1058\", \"label\": \"#1058\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1053\", \"label\": \"#1053\"}]"}
{"id": "changelog:the-internal-database", "page": "changelog", "ref": "the-internal-database", "title": "The _internal database", "content": "As part of ongoing work to help Datasette handle much larger numbers of connected databases and tables (see  Datasette Library ) Datasette now maintains an in-memory SQLite database with details of all of the attached databases, tables, columns, indexes and foreign keys. ( #1150 ) \n                 This will support future improvements such as a searchable, paginated homepage of all available tables. \n                 You can explore an example of this database by  signing in as root  to the  latest.datasette.io  demo instance and then navigating to  latest.datasette.io/_internal . \n                 Plugins can use these tables to introspect attached data in an efficient way. Plugin authors should note that this is not yet considered a stable interface, so any plugins that use this may need to make changes prior to Datasette 1.0 if the  _internal  table schemas change.", "breadcrumbs": "[\"Changelog\", \"0.54 (2021-01-25)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/417\", \"label\": \"Datasette Library\"}, {\"href\": \"https://github.com/simonw/datasette/issues/1150\", \"label\": \"#1150\"}, {\"href\": \"https://latest.datasette.io/login-as-root\", \"label\": \"signing in as root\"}, {\"href\": \"https://latest.datasette.io/_internal\", \"label\": \"latest.datasette.io/_internal\"}]"}
{"id": "changelog:the-road-to-datasette-1-0", "page": "changelog", "ref": "the-road-to-datasette-1-0", "title": "The road to Datasette 1.0", "content": "I've assembled a  milestone for Datasette 1.0 . The focus of the 1.0 release will be the following: \n                 \n                     \n                         Signify confidence in the quality/stability of Datasette \n                     \n                     \n                         Give plugin authors confidence that their plugins will work for the whole 1.x release cycle \n                     \n                     \n                         Provide the same confidence to developers building against Datasette JSON APIs \n                     \n                 \n                 If you have thoughts about what you would like to see for Datasette 1.0 you can join  the conversation on issue #519 .", "breadcrumbs": "[\"Changelog\", \"0.44 (2020-06-11)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/milestone/7\", \"label\": \"milestone for Datasette 1.0\"}, {\"href\": \"https://github.com/simonw/datasette/issues/519\", \"label\": \"the conversation on issue #519\"}]"}
{"id": "changelog:through-for-joins-through-many-to-many-tables", "page": "changelog", "ref": "through-for-joins-through-many-to-many-tables", "title": "?_through= for joins through many-to-many tables", "content": "The new  ?_through={json}  argument to the Table view allows records to be filtered based on a many-to-many relationship. See  Special table arguments  for full documentation - here's  an example . ( #355 ) \n                 This feature was added to help support  facet by many-to-many , which isn't quite ready yet but will be coming in the next Datasette release.", "breadcrumbs": "[\"Changelog\", \"0.29 (2019-07-07)\"]", "references": "[{\"href\": \"https://latest.datasette.io/fixtures/roadside_attractions?_through={%22table%22:%22roadside_attraction_characteristics%22,%22column%22:%22characteristic_id%22,%22value%22:%221%22}\", \"label\": \"an example\"}, {\"href\": \"https://github.com/simonw/datasette/issues/355\", \"label\": \"#355\"}, {\"href\": \"https://github.com/simonw/datasette/issues/551\", \"label\": \"facet by many-to-many\"}]"}
{"id": "changelog:url-building", "page": "changelog", "ref": "url-building", "title": "URL building", "content": "The new  datasette.urls  family of methods can be used to generate URLs to key pages within the Datasette interface, both within custom templates and Datasette plugins. See  Building URLs within plugins  for more details. ( #904 )", "breadcrumbs": "[\"Changelog\", \"0.51 (2020-10-31)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/904\", \"label\": \"#904\"}]"}
{"id": "changelog:v0-28-databases-that-change", "page": "changelog", "ref": "v0-28-databases-that-change", "title": "Supporting databases that change", "content": "From the beginning of the project, Datasette has been designed with read-only databases in mind. If a database is guaranteed not to change it opens up all kinds of interesting opportunities - from taking advantage of SQLite immutable mode and HTTP caching to bundling static copies of the database directly in a Docker container.  The interesting ideas in Datasette  explores this idea in detail. \n                 As my goals for the project have developed, I realized that read-only databases are no longer the right default. SQLite actually supports concurrent access very well provided only one thread attempts to write to a database at a time, and I keep encountering sensible use-cases for running Datasette on top of a database that is processing inserts and updates. \n                 So, as-of version 0.28 Datasette no longer assumes that a database file will not change. It is now safe to point Datasette at a SQLite database which is being updated by another process. \n                 Making this change was a lot of work - see tracking tickets  #418 ,  #419  and  #420 . It required new thinking around how Datasette should calculate table counts (an expensive operation against a large, changing database) and also meant reconsidering the \"content hash\" URLs Datasette has used in the past to optimize the performance of HTTP caches. \n                 Datasette can still run against immutable files and gains numerous performance benefits from doing so, but this is no longer the default behaviour. Take a look at the new  Performance and caching  documentation section for details on how to make the most of Datasette against data that you know will be staying read-only and immutable.", "breadcrumbs": "[\"Changelog\", \"0.28 (2019-05-19)\"]", "references": "[{\"href\": \"https://simonwillison.net/2018/Oct/4/datasette-ideas/\", \"label\": \"The interesting ideas in Datasette\"}, {\"href\": \"https://github.com/simonw/datasette/issues/418\", \"label\": \"#418\"}, {\"href\": \"https://github.com/simonw/datasette/issues/419\", \"label\": \"#419\"}, {\"href\": \"https://github.com/simonw/datasette/issues/420\", \"label\": \"#420\"}]"}
{"id": "changelog:v0-28-faceting", "page": "changelog", "ref": "v0-28-faceting", "title": "Faceting improvements, and faceting plugins", "content": "Datasette  Facets  provide an intuitive way to quickly summarize and interact with data. Previously the only supported faceting technique was column faceting, but 0.28 introduces two powerful new capabilities: facet-by-JSON-array and the ability to define further facet types using plugins. \n                 Facet by array ( #359 ) is only available if your SQLite installation provides the  json1  extension. Datasette will automatically detect columns that contain JSON arrays of values and offer a faceting interface against those columns - useful for modelling things like tags without needing to break them out into a new table. See  Facet by JSON array  for more. \n                 The new  register_facet_classes()  plugin hook ( #445 ) can be used to register additional custom facet classes. Each facet class should provide two methods:  suggest()  which suggests facet selections that might be appropriate for a provided SQL query, and  facet_results()  which executes a facet operation and returns results. Datasette's own faceting implementations have been refactored to use the same API as these plugins.", "breadcrumbs": "[\"Changelog\", \"0.28 (2019-05-19)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues/359\", \"label\": \"#359\"}, {\"href\": \"https://github.com/simonw/datasette/pull/445\", \"label\": \"#445\"}]"}
{"id": "changelog:v0-28-medium-changes", "page": "changelog", "ref": "v0-28-medium-changes", "title": "Medium changes", "content": "Datasette now conforms to the  Black coding style  ( #449 ) - and has a unit test to enforce this in the future \n                     \n                     \n                         \n                             \n                                 New  Special table arguments : \n                                 \n                                     \n                                         \n                                             ?columnname__in=value1,value2,value3  filter for executing SQL IN queries against a table, see  Table arguments  ( #433 ) \n                                         \n                                         \n                                             ?columnname__date=yyyy-mm-dd  filter which returns rows where the spoecified datetime column falls on the specified date ( 583b22a ) \n                                         \n                                         \n                                             ?tags__arraycontains=tag  filter which acts against a JSON array contained in a column ( 78e45ea ) \n                                         \n                                         \n                                             ?_where=sql-fragment  filter for the table view  ( #429 ) \n                                         \n                                         \n                                             ?_fts_table=mytable  and  ?_fts_pk=mycolumn  query string options can be used to specify which FTS table to use for a search query - see  Configuring full-text search for a table or view  ( #428 ) \n                                         \n                                     \n                                 \n                             \n                         \n                     \n                     \n                         You can now pass the same table filter multiple times - for example,  ?content__not=world&content__not=hello  will return all rows where the content column is neither  hello  or  world  ( #288 ) \n                     \n                     \n                         You can now specify  about  and  about_url  metadata (in addition to  source  and  license ) linking to further information about a project - see  Source, license and about \n                     \n                     \n                         New  ?_trace=1  parameter now adds debug information showing every SQL query that was executed while constructing the page ( #435 ) \n                     \n                     \n                         datasette inspect  now just calculates table counts, and does not introspect other database metadata ( #462 ) \n                     \n                     \n                         Removed  /-/inspect  page entirely - this will be replaced by something similar in the future, see  #465 \n                     \n                     \n                         Datasette can now run against an in-memory SQLite database. You can do this by starting it without passing any files or by using the new  --memory  option to  datasette serve . This can be useful for experimenting with SQLite queries that do not access any data, such as  SELECT 1+1  or  SELECT sqlite_version() .", "breadcrumbs": "[\"Changelog\", \"0.28 (2019-05-19)\"]", "references": "[{\"href\": \"https://github.com/python/black\", \"label\": \"Black coding style\"}, {\"href\": \"https://github.com/simonw/datasette/pull/449\", \"label\": \"#449\"}, {\"href\": \"https://github.com/simonw/datasette/issues/433\", \"label\": \"#433\"}, {\"href\": \"https://github.com/simonw/datasette/commit/583b22aa28e26c318de0189312350ab2688c90b1\", \"label\": \"583b22a\"}, {\"href\": \"https://github.com/simonw/datasette/commit/78e45ead4d771007c57b307edf8fc920101f8733\", \"label\": \"78e45ea\"}, {\"href\": \"https://github.com/simonw/datasette/issues/429\", \"label\": \"#429\"}, {\"href\": \"https://github.com/simonw/datasette/issues/428\", \"label\": \"#428\"}, {\"href\": \"https://github.com/simonw/datasette/issues/288\", \"label\": \"#288\"}, {\"href\": \"https://github.com/simonw/datasette/issues/435\", \"label\": \"#435\"}, {\"href\": \"https://github.com/simonw/datasette/issues/462\", \"label\": \"#462\"}, {\"href\": \"https://github.com/simonw/datasette/issues/465\", \"label\": \"#465\"}]"}
{"id": "changelog:v0-28-publish-cloudrun", "page": "changelog", "ref": "v0-28-publish-cloudrun", "title": "datasette publish cloudrun", "content": "Google Cloud Run  is a brand new serverless hosting platform from Google, which allows you to build a Docker container which will run only when HTTP traffic is received and will shut down (and hence cost you nothing) the rest of the time. It's similar to Zeit's Now v1 Docker hosting platform which sadly is  no longer accepting signups  from new users. \n                 The new  datasette publish cloudrun  command was contributed by Romain Primet ( #434 ) and publishes selected databases to a new Datasette instance running on Google Cloud Run. \n                 See  Publishing to Google Cloud Run  for full documentation.", "breadcrumbs": "[\"Changelog\", \"0.28 (2019-05-19)\"]", "references": "[{\"href\": \"https://cloud.google.com/run/\", \"label\": \"Google Cloud Run\"}, {\"href\": \"https://hyperion.alpha.spectrum.chat/zeit/now/cannot-create-now-v1-deployments~d206a0d4-5835-4af5-bb5c-a17f0171fb25?m=MTU0Njk2NzgwODM3OA==\", \"label\": \"no longer accepting signups\"}, {\"href\": \"https://github.com/simonw/datasette/pull/434\", \"label\": \"#434\"}]"}
{"id": "changelog:v0-28-register-output-renderer", "page": "changelog", "ref": "v0-28-register-output-renderer", "title": "register_output_renderer plugins", "content": "Russ Garrett implemented a new Datasette plugin hook called  register_output_renderer  ( #441 ) which allows plugins to create additional output renderers in addition to Datasette's default  .json  and  .csv . \n                 Russ's in-development  datasette-geo  plugin includes  an example  of this hook being used to output  .geojson  automatically converted from SpatiaLite.", "breadcrumbs": "[\"Changelog\", \"0.28 (2019-05-19)\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/pull/441\", \"label\": \"#441\"}, {\"href\": \"https://github.com/russss/datasette-geo\", \"label\": \"datasette-geo\"}, {\"href\": \"https://github.com/russss/datasette-geo/blob/d4cecc020848bbde91e9e17bf352f7c70bc3dccf/datasette_plugin_geo/geojson.py\", \"label\": \"an example\"}]"}
{"id": "changelog:v0-29-medium-changes", "page": "changelog", "ref": "v0-29-medium-changes", "title": "Easier custom templates for table rows", "content": "If you want to customize the display of individual table rows, you can do so using a  _table.html  template include that looks something like this: \n                 {% for row in display_rows %}\n    <div>\n        <h2>{{ row[\"title\"] }}</h2>\n        <p>{{ row[\"description\"] }}<lp>\n        <p>Category: {{ row.display(\"category_id\") }}</p>\n    </div>\n{% endfor %} \n                 This is a  backwards incompatible change . If you previously had a custom template called  _rows_and_columns.html  you need to rename it to  _table.html . \n                 See  Custom templates  for full details.", "breadcrumbs": "[\"Changelog\", \"0.29 (2019-07-07)\"]", "references": "[]"}
{"id": "changelog:writable-canned-queries", "page": "changelog", "ref": "writable-canned-queries", "title": "Writable canned queries", "content": "Datasette's  Canned queries  feature lets you define SQL queries in  metadata.json  which can then be executed by users visiting a specific URL.  https://latest.datasette.io/fixtures/neighborhood_search  for example. \n                 Canned queries were previously restricted to  SELECT , but Datasette 0.44 introduces the ability for canned queries to execute  INSERT  or  UPDATE  queries as well, using the new  \"write\": true  property ( #800 ): \n                 {\n    \"databases\": {\n        \"dogs\": {\n            \"queries\": {\n                \"add_name\": {\n                    \"sql\": \"INSERT INTO names (name) VALUES (:name)\",\n                    \"write\": true\n                }\n            }\n        }\n    }\n} \n                 See  Writable canned queries  for more details.", "breadcrumbs": "[\"Changelog\", \"0.44 (2020-06-11)\"]", "references": "[{\"href\": \"https://latest.datasette.io/fixtures/neighborhood_search\", \"label\": \"https://latest.datasette.io/fixtures/neighborhood_search\"}, {\"href\": \"https://github.com/simonw/datasette/issues/800\", \"label\": \"#800\"}]"}
{"id": "cli-reference:cli-datasette-get", "page": "cli-reference", "ref": "cli-datasette-get", "title": "datasette --get", "content": "The  --get  option to  datasette serve  (or just  datasette ) specifies the path to a page within Datasette and causes Datasette to output the content from that path without starting the web server. \n                 This means that all of Datasette's functionality can be accessed directly from the command-line. \n                 For example: \n                 $ datasette --get '/-/versions.json' | jq .\n{\n  \"python\": {\n    \"version\": \"3.8.5\",\n    \"full\": \"3.8.5 (default, Jul 21 2020, 10:48:26) \\n[Clang 11.0.3 (clang-1103.0.32.62)]\"\n  },\n  \"datasette\": {\n    \"version\": \"0.46+15.g222a84a.dirty\"\n  },\n  \"asgi\": \"3.0\",\n  \"uvicorn\": \"0.11.8\",\n  \"sqlite\": {\n    \"version\": \"3.32.3\",\n    \"fts_versions\": [\n      \"FTS5\",\n      \"FTS4\",\n      \"FTS3\"\n    ],\n    \"extensions\": {\n      \"json1\": null\n    },\n    \"compile_options\": [\n      \"COMPILER=clang-11.0.3\",\n      \"ENABLE_COLUMN_METADATA\",\n      \"ENABLE_FTS3\",\n      \"ENABLE_FTS3_PARENTHESIS\",\n      \"ENABLE_FTS4\",\n      \"ENABLE_FTS5\",\n      \"ENABLE_GEOPOLY\",\n      \"ENABLE_JSON1\",\n      \"ENABLE_PREUPDATE_HOOK\",\n      \"ENABLE_RTREE\",\n      \"ENABLE_SESSION\",\n      \"MAX_VARIABLE_NUMBER=250000\",\n      \"THREADSAFE=1\"\n    ]\n  }\n} \n                 The exit code will be 0 if the request succeeds and 1 if the request produced an HTTP status code other than 200 - e.g. a 404 or 500 error. \n                 This lets you use  datasette --get /  to run tests against a Datasette application in a continuous integration environment such as GitHub Actions.", "breadcrumbs": "[\"CLI reference\", \"datasette serve\"]", "references": "[]"}
{"id": "cli-reference:cli-help-help", "page": "cli-reference", "ref": "cli-help-help", "title": "datasette --help", "content": "Running  datasette --help  shows a list of all of the available commands. \n             [[[cog\nhelp([\"--help\"]) \n             ]]] \n             Usage: datasette [OPTIONS] COMMAND [ARGS]...\n\n  Datasette is an open source multi-tool for exploring and publishing data\n\n  About Datasette: https://datasette.io/\n  Full documentation: https://docs.datasette.io/\n\nOptions:\n  --version  Show the version and exit.\n  --help     Show this message and exit.\n\nCommands:\n  serve*     Serve up specified SQLite database files with a web UI\n  inspect    Generate JSON summary of provided database files\n  install    Install plugins and packages from PyPI into the same...\n  package    Package SQLite files into a Datasette Docker container\n  plugins    List currently installed plugins\n  publish    Publish specified SQLite database files to the internet along...\n  uninstall  Uninstall plugins and Python packages from the Datasette... \n             [[[end]]] \n             Additional commands added by plugins that use the  register_commands(cli)  hook will be listed here as well.", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-inspect-help", "page": "cli-reference", "ref": "cli-help-inspect-help", "title": "datasette inspect", "content": "Outputs JSON representing introspected data about one or more SQLite database files. \n             If you are opening an immutable database, you can pass this file to the  --inspect-data  option to improve Datasette's performance by allowing it to skip running row counts against the database when it first starts running: \n             datasette inspect mydatabase.db > inspect-data.json\ndatasette serve -i mydatabase.db --inspect-file inspect-data.json \n             This performance optimization is used automatically by some of the  datasette publish  commands. You are unlikely to need to apply this optimization manually. \n             [[[cog\nhelp([\"inspect\", \"--help\"]) \n             ]]] \n             Usage: datasette inspect [OPTIONS] [FILES]...\n\n  Generate JSON summary of provided database files\n\n  This can then be passed to \"datasette --inspect-file\" to speed up count\n  operations against immutable database files.\n\nOptions:\n  --inspect-file TEXT\n  --load-extension PATH:ENTRYPOINT?\n                                  Path to a SQLite extension to load, and\n                                  optional entrypoint\n  --help                          Show this message and exit. \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-install-help", "page": "cli-reference", "ref": "cli-help-install-help", "title": "datasette install", "content": "Install new Datasette plugins. This command works like  pip install  but ensures that your plugins will be installed into the same environment as Datasette. \n             This command: \n             datasette install datasette-cluster-map \n             Would install the  datasette-cluster-map  plugin. \n             [[[cog\nhelp([\"install\", \"--help\"]) \n             ]]] \n             Usage: datasette install [OPTIONS] PACKAGES...\n\n  Install plugins and packages from PyPI into the same environment as Datasette\n\nOptions:\n  -U, --upgrade  Upgrade packages to latest version\n  --help         Show this message and exit. \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[{\"href\": \"https://datasette.io/plugins/datasette-cluster-map\", \"label\": \"datasette-cluster-map\"}]"}
{"id": "cli-reference:cli-help-package-help", "page": "cli-reference", "ref": "cli-help-package-help", "title": "datasette package", "content": "Package SQLite files into a Datasette Docker container, see  datasette package . \n             [[[cog\nhelp([\"package\", \"--help\"]) \n             ]]] \n             Usage: datasette package [OPTIONS] FILES...\n\n  Package SQLite files into a Datasette Docker container\n\nOptions:\n  -t, --tag TEXT            Name for the resulting Docker container, can\n                            optionally use name:tag format\n  -m, --metadata FILENAME   Path to JSON/YAML file containing metadata to\n                            publish\n  --extra-options TEXT      Extra options to pass to datasette serve\n  --branch TEXT             Install datasette from a GitHub branch e.g. main\n  --template-dir DIRECTORY  Path to directory containing custom templates\n  --plugins-dir DIRECTORY   Path to directory containing custom plugins\n  --static MOUNT:DIRECTORY  Serve static files from this directory at /MOUNT/...\n  --install TEXT            Additional packages (e.g. plugins) to install\n  --spatialite              Enable SpatialLite extension\n  --version-note TEXT       Additional note to show on /-/versions\n  --secret TEXT             Secret used for signing secure values, such as\n                            signed cookies\n  -p, --port INTEGER RANGE  Port to run the server on, defaults to 8001\n                            [1<=x<=65535]\n  --title TEXT              Title for metadata\n  --license TEXT            License label for metadata\n  --license_url TEXT        License URL for metadata\n  --source TEXT             Source label for metadata\n  --source_url TEXT         Source URL for metadata\n  --about TEXT              About label for metadata\n  --about_url TEXT          About URL for metadata\n  --help                    Show this message and exit. \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-plugins-help", "page": "cli-reference", "ref": "cli-help-plugins-help", "title": "datasette plugins", "content": "Output JSON showing all currently installed plugins, their versions, whether they include static files or templates and which  Plugin hooks  they use. \n             [[[cog\nhelp([\"plugins\", \"--help\"]) \n             ]]] \n             Usage: datasette plugins [OPTIONS]\n\n  List currently installed plugins\n\nOptions:\n  --all                    Include built-in default plugins\n  --plugins-dir DIRECTORY  Path to directory containing custom plugins\n  --help                   Show this message and exit. \n             [[[end]]] \n             Example output: \n             [\n    {\n        \"name\": \"datasette-geojson\",\n        \"static\": false,\n        \"templates\": false,\n        \"version\": \"0.3.1\",\n        \"hooks\": [\n            \"register_output_renderer\"\n        ]\n    },\n    {\n        \"name\": \"datasette-geojson-map\",\n        \"static\": true,\n        \"templates\": false,\n        \"version\": \"0.4.0\",\n        \"hooks\": [\n            \"extra_body_script\",\n            \"extra_css_urls\",\n            \"extra_js_urls\"\n        ]\n    },\n    {\n        \"name\": \"datasette-leaflet\",\n        \"static\": true,\n        \"templates\": false,\n        \"version\": \"0.2.2\",\n        \"hooks\": [\n            \"extra_body_script\",\n            \"extra_template_vars\"\n        ]\n    }\n]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-publish-cloudrun-help", "page": "cli-reference", "ref": "cli-help-publish-cloudrun-help", "title": "datasette publish cloudrun", "content": "See  Publishing to Google Cloud Run . \n             [[[cog\nhelp([\"publish\", \"cloudrun\", \"--help\"]) \n             ]]] \n             Usage: datasette publish cloudrun [OPTIONS] [FILES]...\n\n  Publish databases to Datasette running on Cloud Run\n\nOptions:\n  -m, --metadata FILENAME         Path to JSON/YAML file containing metadata to\n                                  publish\n  --extra-options TEXT            Extra options to pass to datasette serve\n  --branch TEXT                   Install datasette from a GitHub branch e.g.\n                                  main\n  --template-dir DIRECTORY        Path to directory containing custom templates\n  --plugins-dir DIRECTORY         Path to directory containing custom plugins\n  --static MOUNT:DIRECTORY        Serve static files from this directory at\n                                  /MOUNT/...\n  --install TEXT                  Additional packages (e.g. plugins) to install\n  --plugin-secret <TEXT TEXT TEXT>...\n                                  Secrets to pass to plugins, e.g. --plugin-\n                                  secret datasette-auth-github client_id xxx\n  --version-note TEXT             Additional note to show on /-/versions\n  --secret TEXT                   Secret used for signing secure values, such as\n                                  signed cookies\n  --title TEXT                    Title for metadata\n  --license TEXT                  License label for metadata\n  --license_url TEXT              License URL for metadata\n  --source TEXT                   Source label for metadata\n  --source_url TEXT               Source URL for metadata\n  --about TEXT                    About label for metadata\n  --about_url TEXT                About URL for metadata\n  -n, --name TEXT                 Application name to use when building\n  --service TEXT                  Cloud Run service to deploy (or over-write)\n  --spatialite                    Enable SpatialLite extension\n  --show-files                    Output the generated Dockerfile and\n                                  metadata.json\n  --memory TEXT                   Memory to allocate in Cloud Run, e.g. 1Gi\n  --cpu [1|2|4]                   Number of vCPUs to allocate in Cloud Run\n  --timeout INTEGER               Build timeout in seconds\n  --apt-get-install TEXT          Additional packages to apt-get install\n  --max-instances INTEGER         Maximum Cloud Run instances\n  --min-instances INTEGER         Minimum Cloud Run instances\n  --help                          Show this message and exit. \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-publish-help", "page": "cli-reference", "ref": "cli-help-publish-help", "title": "datasette publish", "content": "Shows a list of available deployment targets for  publishing data  with Datasette. \n             Additional deployment targets can be added by plugins that use the  publish_subcommand(publish)  hook. \n             [[[cog\nhelp([\"publish\", \"--help\"]) \n             ]]] \n             Usage: datasette publish [OPTIONS] COMMAND [ARGS]...\n\n  Publish specified SQLite database files to the internet along with a\n  Datasette-powered interface and API\n\nOptions:\n  --help  Show this message and exit.\n\nCommands:\n  cloudrun  Publish databases to Datasette running on Cloud Run\n  heroku    Publish databases to Datasette running on Heroku \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-publish-heroku-help", "page": "cli-reference", "ref": "cli-help-publish-heroku-help", "title": "datasette publish heroku", "content": "See  Publishing to Heroku . \n             [[[cog\nhelp([\"publish\", \"heroku\", \"--help\"]) \n             ]]] \n             Usage: datasette publish heroku [OPTIONS] [FILES]...\n\n  Publish databases to Datasette running on Heroku\n\nOptions:\n  -m, --metadata FILENAME         Path to JSON/YAML file containing metadata to\n                                  publish\n  --extra-options TEXT            Extra options to pass to datasette serve\n  --branch TEXT                   Install datasette from a GitHub branch e.g.\n                                  main\n  --template-dir DIRECTORY        Path to directory containing custom templates\n  --plugins-dir DIRECTORY         Path to directory containing custom plugins\n  --static MOUNT:DIRECTORY        Serve static files from this directory at\n                                  /MOUNT/...\n  --install TEXT                  Additional packages (e.g. plugins) to install\n  --plugin-secret <TEXT TEXT TEXT>...\n                                  Secrets to pass to plugins, e.g. --plugin-\n                                  secret datasette-auth-github client_id xxx\n  --version-note TEXT             Additional note to show on /-/versions\n  --secret TEXT                   Secret used for signing secure values, such as\n                                  signed cookies\n  --title TEXT                    Title for metadata\n  --license TEXT                  License label for metadata\n  --license_url TEXT              License URL for metadata\n  --source TEXT                   Source label for metadata\n  --source_url TEXT               Source URL for metadata\n  --about TEXT                    About label for metadata\n  --about_url TEXT                About URL for metadata\n  -n, --name TEXT                 Application name to use when deploying\n  --tar TEXT                      --tar option to pass to Heroku, e.g.\n                                  --tar=/usr/local/bin/gtar\n  --generate-dir DIRECTORY        Output generated application files and stop\n                                  without deploying\n  --help                          Show this message and exit. \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-serve-help", "page": "cli-reference", "ref": "cli-help-serve-help", "title": "datasette serve", "content": "This command starts the Datasette web application running on your machine: \n             datasette serve mydatabase.db \n             Or since this is the default command you can run this instead: \n             datasette mydatabase.db \n             Once started you can access it at  http://localhost:8001 \n             [[[cog\nhelp([\"serve\", \"--help\"]) \n             ]]] \n             Usage: datasette serve [OPTIONS] [FILES]...\n\n  Serve up specified SQLite database files with a web UI\n\nOptions:\n  -i, --immutable PATH            Database files to open in immutable mode\n  -h, --host TEXT                 Host for server. Defaults to 127.0.0.1 which\n                                  means only connections from the local machine\n                                  will be allowed. Use 0.0.0.0 to listen to all\n                                  IPs and allow access from other machines.\n  -p, --port INTEGER RANGE        Port for server, defaults to 8001. Use -p 0 to\n                                  automatically assign an available port.\n                                  [0<=x<=65535]\n  --uds TEXT                      Bind to a Unix domain socket\n  --reload                        Automatically reload if code or metadata\n                                  change detected - useful for development\n  --cors                          Enable CORS by serving Access-Control-Allow-\n                                  Origin: *\n  --load-extension PATH:ENTRYPOINT?\n                                  Path to a SQLite extension to load, and\n                                  optional entrypoint\n  --inspect-file TEXT             Path to JSON file created using \"datasette\n                                  inspect\"\n  -m, --metadata FILENAME         Path to JSON/YAML file containing\n                                  license/source metadata\n  --template-dir DIRECTORY        Path to directory containing custom templates\n  --plugins-dir DIRECTORY         Path to directory containing custom plugins\n  --static MOUNT:DIRECTORY        Serve static files from this directory at\n                                  /MOUNT/...\n  --memory                        Make /_memory database available\n  --config CONFIG                 Deprecated: set config option using\n                                  configname:value. Use --setting instead.\n  --setting SETTING...            Setting, see\n                                  docs.datasette.io/en/stable/settings.html\n  --secret TEXT                   Secret used for signing secure values, such as\n                                  signed cookies\n  --root                          Output URL that sets a cookie authenticating\n                                  the root user\n  --get TEXT                      Run an HTTP GET request against this path,\n                                  print results and exit\n  --version-note TEXT             Additional note to show on /-/versions\n  --help-settings                 Show available settings\n  --pdb                           Launch debugger on any errors\n  -o, --open                      Open Datasette in your web browser\n  --create                        Create database files if they do not exist\n  --crossdb                       Enable cross-database joins using the /_memory\n                                  database\n  --nolock                        Ignore locking, open locked files in read-only\n                                  mode\n  --ssl-keyfile TEXT              SSL key file\n  --ssl-certfile TEXT             SSL certificate file\n  --help                          Show this message and exit. \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:cli-help-serve-help-settings", "page": "cli-reference", "ref": "cli-help-serve-help-settings", "title": "datasette serve --help-settings", "content": "This command outputs all of the available Datasette  settings . \n                 These can be passed to  datasette serve  using  datasette serve --setting name value . \n                 [[[cog\nhelp([\"--help-settings\"]) \n                 ]]] \n                 Settings:\n  default_page_size            Default page size for the table view\n                               (default=100)\n  max_returned_rows            Maximum rows that can be returned from a table or\n                               custom query (default=1000)\n  num_sql_threads              Number of threads in the thread pool for\n                               executing SQLite queries (default=3)\n  sql_time_limit_ms            Time limit for a SQL query in milliseconds\n                               (default=1000)\n  default_facet_size           Number of values to return for requested facets\n                               (default=30)\n  facet_time_limit_ms          Time limit for calculating a requested facet\n                               (default=200)\n  facet_suggest_time_limit_ms  Time limit for calculating a suggested facet\n                               (default=50)\n  allow_facet                  Allow users to specify columns to facet using\n                               ?_facet= parameter (default=True)\n  default_allow_sql            Allow anyone to run arbitrary SQL queries\n                               (default=True)\n  allow_download               Allow users to download the original SQLite\n                               database files (default=True)\n  suggest_facets               Calculate and display suggested facets\n                               (default=True)\n  default_cache_ttl            Default HTTP cache TTL (used in Cache-Control:\n                               max-age= header) (default=5)\n  cache_size_kb                SQLite cache size in KB (0 == use SQLite default)\n                               (default=0)\n  allow_csv_stream             Allow .csv?_stream=1 to download all rows\n                               (ignoring max_returned_rows) (default=True)\n  max_csv_mb                   Maximum size allowed for CSV export in MB - set 0\n                               to disable this limit (default=100)\n  truncate_cells_html          Truncate cells longer than this in HTML table\n                               view - set 0 to disable (default=2048)\n  force_https_urls             Force URLs in API output to always use https://\n                               protocol (default=False)\n  template_debug               Allow display of template debug information with\n                               ?_context=1 (default=False)\n  trace_debug                  Allow display of SQL trace debug information with\n                               ?_trace=1 (default=False)\n  base_url                     Datasette URLs should use this base path\n                               (default=/) \n                 [[[end]]]", "breadcrumbs": "[\"CLI reference\", \"datasette serve\"]", "references": "[]"}
{"id": "cli-reference:cli-help-uninstall-help", "page": "cli-reference", "ref": "cli-help-uninstall-help", "title": "datasette uninstall", "content": "Uninstall one or more plugins. \n             [[[cog\nhelp([\"uninstall\", \"--help\"]) \n             ]]] \n             Usage: datasette uninstall [OPTIONS] PACKAGES...\n\n  Uninstall plugins and Python packages from the Datasette environment\n\nOptions:\n  -y, --yes  Don't ask for confirmation\n  --help     Show this message and exit. \n             [[[end]]]", "breadcrumbs": "[\"CLI reference\"]", "references": "[]"}
{"id": "cli-reference:id1", "page": "cli-reference", "ref": "id1", "title": "CLI reference", "content": "The  datasette  CLI tool provides a number of commands. \n         Running  datasette  without specifying a command runs the default command,  datasette serve .  See  datasette serve  for the full list of options for that command. \n         [[[cog\nfrom datasette import cli\nfrom click.testing import CliRunner\nimport textwrap\ndef help(args):\n    title = \"datasette \" + \" \".join(args)\n    cog.out(\"\\n::\\n\\n\")\n    result = CliRunner().invoke(cli.cli, args)\n    output = result.output.replace(\"Usage: cli \", \"Usage: datasette \")\n    cog.out(textwrap.indent(output, '    '))\n    cog.out(\"\\n\\n\") \n         ]]] \n         [[[end]]]", "breadcrumbs": "[]", "references": "[]"}
{"id": "contributing:contributing-alpha-beta", "page": "contributing", "ref": "contributing-alpha-beta", "title": "Alpha and beta releases", "content": "Alpha and beta releases are published to preview upcoming features that may not yet be stable - in particular to preview new plugin hooks. \n             You are welcome to try these out, but please be aware that details may change before the final release. \n             Please join  discussions on the issue tracker  to share your thoughts and experiences with on alpha and beta features that you try out.", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/issues\", \"label\": \"discussions on the issue tracker\"}]"}
{"id": "contributing:contributing-bug-fix-branch", "page": "contributing", "ref": "contributing-bug-fix-branch", "title": "Releasing bug fixes from a branch", "content": "If it's necessary to publish a bug fix release without shipping new features that have landed on  main  a release branch can be used. \n             Create it from the relevant last tagged release like so: \n             git branch 0.52.x 0.52.4\ngit checkout 0.52.x \n             Next cherry-pick the commits containing the bug fixes: \n             git cherry-pick COMMIT \n             Write the release notes in the branch, and update the version number in  version.py . Then push the branch: \n             git push -u origin 0.52.x \n             Once the tests have completed, publish the release from that branch target using the GitHub  Draft a new release  form. \n             Finally, cherry-pick the commit with the release notes and version number bump across to  main : \n             git checkout main\ngit cherry-pick COMMIT\ngit push", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/releases/new\", \"label\": \"Draft a new release\"}]"}
{"id": "contributing:contributing-continuous-deployment", "page": "contributing", "ref": "contributing-continuous-deployment", "title": "Continuously deployed demo instances", "content": "The demo instance at  latest.datasette.io  is re-deployed automatically to Google Cloud Run for every push to  main  that passes the test suite. This is implemented by the GitHub Actions workflow at  .github/workflows/deploy-latest.yml . \n             Specific branches can also be set to automatically deploy by adding them to the  on: push: branches  block at the top of the workflow YAML file. Branches configured in this way will be deployed to a new Cloud Run service whether or not their tests pass. \n             The Cloud Run URL for a branch demo can be found in the GitHub Actions logs.", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://latest.datasette.io/\", \"label\": \"latest.datasette.io\"}, {\"href\": \"https://github.com/simonw/datasette/blob/main/.github/workflows/deploy-latest.yml\", \"label\": \".github/workflows/deploy-latest.yml\"}]"}
{"id": "contributing:contributing-debugging", "page": "contributing", "ref": "contributing-debugging", "title": "Debugging", "content": "Any errors that occur while Datasette is running while display a stack trace on the console. \n             You can tell Datasette to open an interactive  pdb  debugger session if an error occurs using the  --pdb  option: \n             datasette --pdb fixtures.db", "breadcrumbs": "[\"Contributing\"]", "references": "[]"}
{"id": "contributing:contributing-documentation", "page": "contributing", "ref": "contributing-documentation", "title": "Editing and building the documentation", "content": "Datasette's documentation lives in the  docs/  directory and is deployed automatically using  Read The Docs . \n             The documentation is written using reStructuredText. You may find this article on  The subset of reStructuredText worth committing to memory  useful. \n             You can build it locally by installing  sphinx  and  sphinx_rtd_theme  in your Datasette development environment and then running  make html  directly in the  docs/  directory: \n             # You may first need to activate your virtual environment:\nsource venv/bin/activate\n\n# Install the dependencies needed to build the docs\npip install -e .[docs]\n\n# Now build the docs\ncd docs/\nmake html \n             This will create the HTML version of the documentation in  docs/_build/html . You can open it in your browser like so: \n             open _build/html/index.html \n             Any time you make changes to a  .rst  file you can re-run  make html  to update the built documents, then refresh them in your browser. \n             For added productivity, you can use use  sphinx-autobuild  to run Sphinx in auto-build mode. This will run a local webserver serving the docs that automatically rebuilds them and refreshes the page any time you hit save in your editor. \n             sphinx-autobuild  will have been installed when you ran  pip install -e .[docs] . In your  docs/  directory you can start the server by running the following: \n             make livehtml \n             Now browse to  http://localhost:8000/  to view the documentation. Any edits you make should be instantly reflected in your browser.", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://readthedocs.org/\", \"label\": \"Read The Docs\"}, {\"href\": \"https://simonwillison.net/2018/Aug/25/restructuredtext/\", \"label\": \"The subset of reStructuredText worth committing to memory\"}, {\"href\": \"https://pypi.org/project/sphinx-autobuild/\", \"label\": \"sphinx-autobuild\"}]"}
{"id": "contributing:contributing-documentation-cog", "page": "contributing", "ref": "contributing-documentation-cog", "title": "Running Cog", "content": "Some pages of documentation (in particular the  CLI reference ) are automatically updated using  Cog . \n                 To update these pages, run the following command: \n                 cog -r docs/*.rst", "breadcrumbs": "[\"Contributing\", \"Editing and building the documentation\"]", "references": "[{\"href\": \"https://github.com/nedbat/cog\", \"label\": \"Cog\"}]"}
{"id": "contributing:contributing-formatting", "page": "contributing", "ref": "contributing-formatting", "title": "Code formatting", "content": "Datasette uses opinionated code formatters:  Black  for Python and  Prettier  for JavaScript. \n             These formatters are enforced by Datasette's continuous integration: if a commit includes Python or JavaScript code that does not match the style enforced by those tools, the tests will fail. \n             When developing locally, you can verify and correct the formatting of your code using these tools.", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://github.com/psf/black\", \"label\": \"Black\"}, {\"href\": \"https://prettier.io/\", \"label\": \"Prettier\"}]"}
{"id": "contributing:contributing-formatting-black", "page": "contributing", "ref": "contributing-formatting-black", "title": "Running Black", "content": "Black will be installed when you run  pip install -e '.[test]' . To test that your code complies with Black, run the following in your root  datasette  repository checkout: \n                 $ black . --check\nAll done! \u2728 \ud83c\udf70 \u2728\n95 files would be left unchanged. \n                 If any of your code does not conform to Black you can run this to automatically fix those problems: \n                 $ black .\nreformatted ../datasette/setup.py\nAll done! \u2728 \ud83c\udf70 \u2728\n1 file reformatted, 94 files left unchanged.", "breadcrumbs": "[\"Contributing\", \"Code formatting\"]", "references": "[]"}
{"id": "contributing:contributing-formatting-blacken-docs", "page": "contributing", "ref": "contributing-formatting-blacken-docs", "title": "blacken-docs", "content": "The  blacken-docs  command applies Black formatting rules to code examples in the documentation. Run it like this: \n                 blacken-docs -l 60 docs/*.rst", "breadcrumbs": "[\"Contributing\", \"Code formatting\"]", "references": "[{\"href\": \"https://pypi.org/project/blacken-docs/\", \"label\": \"blacken-docs\"}]"}
{"id": "contributing:contributing-formatting-prettier", "page": "contributing", "ref": "contributing-formatting-prettier", "title": "Prettier", "content": "To install Prettier,  install Node.js  and then run the following in the root of your  datasette  repository checkout: \n                 $ npm install \n                 This will install Prettier in a  node_modules  directory. You can then check that your code matches the coding style like so: \n                 $ npm run prettier -- --check\n> prettier\n> prettier 'datasette/static/*[!.min].js' \"--check\"\n\nChecking formatting...\n[warn] datasette/static/plugins.js\n[warn] Code style issues found in the above file(s). Forgot to run Prettier? \n                 You can fix any problems by running: \n                 $ npm run fix", "breadcrumbs": "[\"Contributing\", \"Code formatting\"]", "references": "[{\"href\": \"https://nodejs.org/en/download/package-manager/\", \"label\": \"install Node.js\"}]"}
{"id": "contributing:contributing-release", "page": "contributing", "ref": "contributing-release", "title": "Release process", "content": "Datasette releases are performed using tags. When a new release is published on GitHub, a  GitHub Action workflow  will perform the following: \n             \n                 \n                     Run the unit tests against all supported Python versions. If the tests pass... \n                 \n                 \n                     Build a Docker image of the release and push a tag to  https://hub.docker.com/r/datasetteproject/datasette \n                 \n                 \n                     Re-point the \"latest\" tag on Docker Hub to the new image \n                 \n                 \n                     Build a wheel bundle of the underlying Python source code \n                 \n                 \n                     Push that new wheel up to PyPI:  https://pypi.org/project/datasette/ \n                 \n             \n             To deploy new releases you will need to have push access to the main Datasette GitHub repository. \n             Datasette follows  Semantic Versioning : \n             major.minor.patch \n             We increment  major  for backwards-incompatible releases. Datasette is currently pre-1.0 so the major version is always  0 . \n             We increment  minor  for new features. \n             We increment  patch  for bugfix releass. \n             Alpha and beta releases  may have an additional  a0  or  b0  prefix - the integer component will be incremented with each subsequent alpha or beta. \n             To release a new version, first create a commit that updates the version number in  datasette/version.py  and the  the changelog  with highlights of the new version. An example  commit can be seen here : \n             # Update changelog\ngit commit -m \" Release 0.51a1\n\nRefs #1056, #1039, #998, #1045, #1033, #1036, #1034, #976, #1057, #1058, #1053, #1064, #1066\" -a\ngit push \n             Referencing the issues that are part of the release in the commit message ensures the name of the release shows up on those issue pages, e.g.  here . \n             You can generate the list of issue references for a specific release by copying and pasting text from the release notes or GitHub changes-since-last-release view into this  Extract issue numbers from pasted text  tool. \n             To create the tag for the release, create  a new release  on GitHub matching the new version number. You can convert the release notes to Markdown by copying and pasting the rendered HTML into this  Paste to Markdown tool . \n             Finally, post a news item about the release on  datasette.io  by editing the  news.yaml  file in that site's repository.", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/blob/main/.github/workflows/deploy-latest.yml\", \"label\": \"GitHub Action workflow\"}, {\"href\": \"https://hub.docker.com/r/datasetteproject/datasette\", \"label\": \"https://hub.docker.com/r/datasetteproject/datasette\"}, {\"href\": \"https://pypi.org/project/datasette/\", \"label\": \"https://pypi.org/project/datasette/\"}, {\"href\": \"https://semver.org/\", \"label\": \"Semantic Versioning\"}, {\"href\": \"https://github.com/simonw/datasette/commit/0e1e89c6ba3d0fbdb0823272952cf356f3016def\", \"label\": \"commit can be seen here\"}, {\"href\": \"https://github.com/simonw/datasette/issues/581#ref-commit-d56f402\", \"label\": \"here\"}, {\"href\": \"https://observablehq.com/@simonw/extract-issue-numbers-from-pasted-text\", \"label\": \"Extract issue numbers from pasted text\"}, {\"href\": \"https://github.com/simonw/datasette/releases/new\", \"label\": \"a new release\"}, {\"href\": \"https://euangoddard.github.io/clipboard2markdown/\", \"label\": \"Paste to Markdown tool\"}, {\"href\": \"https://datasette.io/\", \"label\": \"datasette.io\"}, {\"href\": \"https://github.com/simonw/datasette.io/blob/main/news.yaml\", \"label\": \"news.yaml\"}]"}
{"id": "contributing:contributing-running-tests", "page": "contributing", "ref": "contributing-running-tests", "title": "Running the tests", "content": "Once you have done this, you can run the Datasette unit tests from inside your  datasette/  directory using  pytest  like so: \n             pytest \n             You can run the tests faster using multiple CPU cores with  pytest-xdist  like this: \n             pytest -n auto -m \"not serial\" \n             -n auto  detects the number of available cores automatically. The  -m \"not serial\"  skips tests that don't work well in a parallel test environment. You can run those tests separately like so: \n             pytest -m \"serial\"", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://docs.pytest.org/\", \"label\": \"pytest\"}, {\"href\": \"https://pypi.org/project/pytest-xdist/\", \"label\": \"pytest-xdist\"}]"}
{"id": "contributing:contributing-upgrading-codemirror", "page": "contributing", "ref": "contributing-upgrading-codemirror", "title": "Upgrading CodeMirror", "content": "Datasette bundles  CodeMirror  for the SQL editing interface, e.g. on  this page . Here are the steps for upgrading to a new version of CodeMirror: \n             \n                 \n                     Download and extract latest CodeMirror zip file from  https://codemirror.net/codemirror.zip \n                 \n                 \n                     Rename  lib/codemirror.js  to  codemirror-5.57.0.js  (using latest version number) \n                 \n                 \n                     Rename  lib/codemirror.css  to  codemirror-5.57.0.css \n                 \n                 \n                     Rename  mode/sql/sql.js  to  codemirror-5.57.0-sql.js \n                 \n                 \n                     Edit both JavaScript files to make the top license comment a  /* */  block instead of multiple  //  lines \n                 \n                 \n                     Minify the JavaScript files like this: \n                     npx uglify-js codemirror-5.57.0.js -o codemirror-5.57.0.min.js --comments '/LICENSE/'\nnpx uglify-js codemirror-5.57.0-sql.js -o codemirror-5.57.0-sql.min.js --comments '/LICENSE/' \n                 \n                 \n                     Check that the LICENSE comment did indeed survive minification \n                 \n                 \n                     Minify the CSS file like this: \n                     npx clean-css-cli codemirror-5.57.0.css -o codemirror-5.57.0.min.css \n                 \n                 \n                     Edit the  _codemirror.html  template to reference the new files \n                 \n                 \n                     git rm  the old files,  git add  the new files", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://codemirror.net/\", \"label\": \"CodeMirror\"}, {\"href\": \"https://latest.datasette.io/fixtures\", \"label\": \"this page\"}, {\"href\": \"https://codemirror.net/codemirror.zip\", \"label\": \"https://codemirror.net/codemirror.zip\"}]"}
{"id": "contributing:contributing-using-fixtures", "page": "contributing", "ref": "contributing-using-fixtures", "title": "Using fixtures", "content": "To run Datasette itself, type  datasette . \n             You're going to need at least one SQLite database. A quick way to get started is to use the fixtures database that Datasette uses for its own tests. \n             You can create a copy of that database by running this command: \n             python tests/fixtures.py fixtures.db \n             Now you can run Datasette against the new fixtures database like so: \n             datasette fixtures.db \n             This will start a server at  http://127.0.0.1:8001/ . \n             Any changes you make in the  datasette/templates  or  datasette/static  folder will be picked up immediately (though you may need to do a force-refresh in your browser to see changes to CSS or JavaScript). \n             If you want to change Datasette's Python code you can use the  --reload  option to cause Datasette to automatically reload any time the underlying code changes: \n             datasette --reload fixtures.db \n             You can also use the  fixtures.py  script to recreate the testing version of  metadata.json  used by the unit tests. To do that: \n             python tests/fixtures.py fixtures.db fixtures-metadata.json \n             Or to output the plugins used by the tests, run this: \n             python tests/fixtures.py fixtures.db fixtures-metadata.json fixtures-plugins\nTest tables written to fixtures.db\n- metadata written to fixtures-metadata.json\nWrote plugin: fixtures-plugins/register_output_renderer.py\nWrote plugin: fixtures-plugins/view_name.py\nWrote plugin: fixtures-plugins/my_plugin.py\nWrote plugin: fixtures-plugins/messages_output_renderer.py\nWrote plugin: fixtures-plugins/my_plugin_2.py \n             Then run Datasette like this: \n             datasette fixtures.db -m fixtures-metadata.json --plugins-dir=fixtures-plugins/", "breadcrumbs": "[\"Contributing\"]", "references": "[]"}
{"id": "contributing:devenvironment", "page": "contributing", "ref": "devenvironment", "title": "Setting up a development environment", "content": "If you have Python 3.7 or higher installed on your computer (on OS X the quickest way to do this  is using homebrew ) you can install an editable copy of Datasette using the following steps. \n             If you want to use GitHub to publish your changes, first  create a fork of datasette  under your own GitHub account. \n             Now clone that repository somewhere on your computer: \n             git clone git@github.com:YOURNAME/datasette \n             If you want to get started without creating your own fork, you can do this instead: \n             git clone git@github.com:simonw/datasette \n             The next step is to create a virtual environment for your project and use it to install Datasette's dependencies: \n             cd datasette\n# Create a virtual environment in ./venv\npython3 -m venv ./venv\n# Now activate the virtual environment, so pip can install into it\nsource venv/bin/activate\n# Install Datasette and its testing dependencies\npython3 -m pip install -e '.[test]' \n             That last line does most of the work:  pip install -e  means \"install this package in a way that allows me to edit the source code in place\". The  .[test]  option means \"use the setup.py in this directory and install the optional testing dependencies as well\".", "breadcrumbs": "[\"Contributing\"]", "references": "[{\"href\": \"https://docs.python-guide.org/starting/install3/osx/\", \"label\": \"is using homebrew\"}, {\"href\": \"https://github.com/simonw/datasette/fork\", \"label\": \"create a fork of datasette\"}]"}
{"id": "contributing:general-guidelines", "page": "contributing", "ref": "general-guidelines", "title": "General guidelines", "content": "main should always be releasable . Incomplete features should live in branches. This ensures that any small bug fixes can be quickly released. \n                 \n                 \n                     The ideal commit  should bundle together the implementation, unit tests and associated documentation updates. The commit message should link to an associated issue. \n                 \n                 \n                     New plugin hooks  should only be shipped if accompanied by a separate release of a non-demo plugin that uses them.", "breadcrumbs": "[\"Contributing\"]", "references": "[]"}
{"id": "contributing:id1", "page": "contributing", "ref": "id1", "title": "Contributing", "content": "Datasette is an open source project. We welcome contributions! \n         This document describes how to contribute to Datasette core. You can also contribute to the wider Datasette ecosystem by creating new  Plugins .", "breadcrumbs": "[]", "references": "[]"}
{"id": "csv_export:csv-export-url-parameters", "page": "csv_export", "ref": "csv-export-url-parameters", "title": "URL parameters", "content": "The following options can be used to customize the CSVs returned by Datasette. \n             \n                 \n                     ?_header=off \n                     \n                         This removes the first row of the CSV file specifying the headings - only the row data will be returned. \n                     \n                 \n                 \n                     ?_stream=on \n                     \n                         Stream all matching records, not just the first page of results. See below. \n                     \n                 \n                 \n                     ?_dl=on \n                     \n                         Causes Datasette to return a  content-disposition: attachment; filename=\"filename.csv\"  header.", "breadcrumbs": "[\"CSV export\"]", "references": "[]"}
{"id": "csv_export:id1", "page": "csv_export", "ref": "id1", "title": "CSV export", "content": "Any Datasette table, view or custom SQL query can be exported as CSV. \n         To obtain the CSV representation of the table you are looking, click the \"this\n            data as CSV\" link. \n         You can also use the advanced export form for more control over the resulting\n            file, which looks like this and has the following options: \n         \n         \n             \n                 download file  - instead of displaying CSV in your browser, this forces\n                    your browser to download the CSV to your downloads directory. \n             \n             \n                 expand labels  - if your table has any foreign key references this option\n                    will cause the CSV to gain additional  COLUMN_NAME_label  columns with a\n                    label for each foreign key derived from the linked table.  In this example \n                    the  city_id  column is accompanied by a  city_id_label  column. \n             \n             \n                 stream all rows  - by default CSV files only contain the first\n                     max_returned_rows  records. This option will cause Datasette to\n                    loop through every matching record and return them as a single CSV file. \n             \n         \n         You can try that out on  https://latest.datasette.io/fixtures/facetable?_size=4", "breadcrumbs": "[]", "references": "[{\"href\": \"https://latest.datasette.io/fixtures/facetable.csv?_labels=on&_size=max\", \"label\": \"In this example\"}, {\"href\": \"https://latest.datasette.io/fixtures/facetable?_size=4\", \"label\": \"https://latest.datasette.io/fixtures/facetable?_size=4\"}]"}
{"id": "csv_export:streaming-all-records", "page": "csv_export", "ref": "streaming-all-records", "title": "Streaming all records", "content": "The  stream all rows  option is designed to be as efficient as possible -\n                under the hood it takes advantage of Python 3 asyncio capabilities and\n                Datasette's efficient  pagination  to stream back the full\n                CSV file. \n             Since databases can get pretty large, by default this option is capped at 100MB -\n                if a table returns more than 100MB of data the last line of the CSV will be a\n                truncation error message. \n             You can increase or remove this limit using the  max_csv_mb  config\n                setting. You can also disable the CSV export feature entirely using\n                 allow_csv_stream .", "breadcrumbs": "[\"CSV export\"]", "references": "[]"}
{"id": "custom_templates:css-classes-on-the-body", "page": "custom_templates", "ref": "css-classes-on-the-body", "title": "CSS classes on the <body>", "content": "Every default template includes CSS classes in the body designed to support\n                    custom styling. \n                 The index template (the top level page at  / ) gets this: \n                 <body class=\"index\"> \n                 The database template ( /dbname ) gets this: \n                 <body class=\"db db-dbname\"> \n                 The custom SQL template ( /dbname?sql=... ) gets this: \n                 <body class=\"query db-dbname\"> \n                 A canned query template ( /dbname/queryname ) gets this: \n                 <body class=\"query db-dbname query-queryname\"> \n                 The table template ( /dbname/tablename ) gets: \n                 <body class=\"table db-dbname table-tablename\"> \n                 The row template ( /dbname/tablename/rowid ) gets: \n                 <body class=\"row db-dbname table-tablename\"> \n                 The  db-x  and  table-x  classes use the database or table names themselves if\n                    they are valid CSS identifiers. If they aren't, we strip any invalid\n                    characters out and append a 6 character md5 digest of the original name, in\n                    order to ensure that multiple tables which resolve to the same stripped\n                    character version still have different CSS classes. \n                 Some examples: \n                 \"simple\" => \"simple\"\n\"MixedCase\" => \"MixedCase\"\n\"-no-leading-hyphens\" => \"no-leading-hyphens-65bea6\"\n\"_no-leading-underscores\" => \"no-leading-underscores-b921bc\"\n\"no spaces\" => \"no-spaces-7088d7\"\n\"-\" => \"336d5e\"\n\"no $ characters\" => \"no--characters-59e024\" \n                 <td>  and  <th>  elements also get custom CSS classes reflecting the\n                    database column they are representing, for example: \n                 <table>\n    <thead>\n        <tr>\n            <th class=\"col-id\" scope=\"col\">id</th>\n            <th class=\"col-name\" scope=\"col\">name</th>\n        </tr>\n    </thead>\n    <tbody>\n        <tr>\n            <td class=\"col-id\"><a href=\"...\">1</a></td>\n            <td class=\"col-name\">SMITH</td>\n        </tr>\n    </tbody>\n</table>", "breadcrumbs": "[\"Custom pages and templates\", \"Custom CSS and JavaScript\"]", "references": "[]"}
{"id": "custom_templates:custom-pages-404", "page": "custom_templates", "ref": "custom-pages-404", "title": "Returning 404s", "content": "To indicate that content could not be found and display the default 404 page you can use the  raise_404(message)  function: \n                 {% if not rows %}\n    {{ raise_404(\"Content not found\") }}\n{% endif %} \n                 If you call  raise_404()  the other content in your template will be ignored.", "breadcrumbs": "[\"Custom pages and templates\", \"Custom pages\"]", "references": "[]"}
{"id": "custom_templates:custom-pages-errors", "page": "custom_templates", "ref": "custom-pages-errors", "title": "Custom error pages", "content": "Datasette returns an error page if an unexpected error occurs, access is forbidden or content cannot be found. \n             You can customize the response returned for these errors by providing a custom error page template. \n             Content not found errors use a  404.html  template. Access denied errors use  403.html . Invalid input errors use  400.html . Unexpected errors of other kinds use  500.html . \n             If a template for the specific error code is not found a template called  error.html  will be used instead. If you do not provide that template Datasette's  default error.html template  will be used. \n             The error template will be passed the following context: \n             \n                 \n                     status  - integer \n                     \n                         The integer HTTP status code, e.g. 404, 500, 403, 400. \n                     \n                 \n                 \n                     error  - string \n                     \n                         Details of the specific error, usually a full sentence. \n                     \n                 \n                 \n                     title  - string or None \n                     \n                         A title for the page representing the class of error. This is often  None  for errors that do not provide a title separate from their  error  message.", "breadcrumbs": "[\"Custom pages and templates\"]", "references": "[{\"href\": \"https://github.com/simonw/datasette/blob/main/datasette/templates/error.html\", \"label\": \"default error.html template\"}]"}