{"rowid": 378, "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", "sections_fts": 698, "rank": null}
{"rowid": 377, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 376, "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", "sections_fts": 698, "rank": null}
{"rowid": 375, "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 .", "sections_fts": 698, "rank": null}
{"rowid": 374, "title": "0.27.1 (2019-05-09)", "content": "Tiny bugfix release: don't install  tests/  in the wrong place. Thanks, Veit Heller.", "sections_fts": 698, "rank": null}
{"rowid": 373, "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", "sections_fts": 698, "rank": null}
{"rowid": 372, "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() .", "sections_fts": 698, "rank": null}
{"rowid": 371, "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.", "sections_fts": 698, "rank": null}
{"rowid": 370, "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.", "sections_fts": 698, "rank": null}
{"rowid": 369, "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.", "sections_fts": 698, "rank": null}
{"rowid": 368, "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.", "sections_fts": 698, "rank": null}
{"rowid": 367, "title": "0.28 (2019-05-19)", "content": "A  salmagundi  of new features!", "sections_fts": 698, "rank": null}
{"rowid": 366, "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.", "sections_fts": 698, "rank": null}
{"rowid": 365, "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.", "sections_fts": 698, "rank": null}
{"rowid": 364, "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.", "sections_fts": 698, "rank": null}
{"rowid": 363, "title": "Facet by date", "content": "If a column contains datetime values, Datasette can now facet that column by date. ( #481 )", "sections_fts": 698, "rank": null}
{"rowid": 362, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 361, "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 ).", "sections_fts": 698, "rank": null}
{"rowid": 360, "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.", "sections_fts": 698, "rank": null}
{"rowid": 359, "title": "ASGI", "content": "ASGI  is the Asynchronous Server Gateway Interface standard. I've been wanting to convert Datasette into an ASGI application for over a year -  Port Datasette to ASGI #272  tracks thirteen months of intermittent development - but with Datasette 0.29 the change is finally released. This also means Datasette now runs on top of  Uvicorn  and no longer depends on  Sanic . \n                 I wrote about the significance of this change in  Porting Datasette to ASGI, and Turtles all the way down . \n                 The most exciting consequence of this change is that Datasette plugins can now take advantage of the ASGI standard.", "sections_fts": 698, "rank": null}
{"rowid": 358, "title": "0.29 (2019-07-07)", "content": "ASGI, new plugin hooks, facet by date and much, much more...", "sections_fts": 698, "rank": null}
{"rowid": 357, "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!", "sections_fts": 698, "rank": null}
{"rowid": 356, "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.", "sections_fts": 698, "rank": null}
{"rowid": 355, "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 .", "sections_fts": 698, "rank": null}
{"rowid": 354, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 353, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 352, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 351, "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.", "sections_fts": 698, "rank": null}
{"rowid": 350, "title": "0.31.1 (2019-11-12)", "content": "Deployments created using  datasette publish   now use  python:3.8  base Docker image ( #629 )", "sections_fts": 698, "rank": null}
{"rowid": 349, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 348, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 347, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 346, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 345, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 344, "title": "0.36 (2020-02-21)", "content": "The  datasette  object passed to plugins now has API documentation:  Datasette class . ( #576 ) \n                 \n                 \n                     New methods on  datasette :  .add_database()  and  .remove_database()  -  documentation . ( #671 ) \n                 \n                 \n                     prepare_connection()  plugin hook now takes optional  datasette  and  database  arguments -  prepare_connection(conn, database, datasette) . ( #678 ) \n                 \n                 \n                     Added three new plugins and one new conversion tool to the  The Datasette Ecosystem .", "sections_fts": 698, "rank": null}
{"rowid": 343, "title": "0.37 (2020-02-25)", "content": "Plugins now have a supported mechanism for writing to a database, using the new  .execute_write()  and  .execute_write_fn()  methods.  Documentation . ( #682 ) \n                 \n                 \n                     Immutable databases that have had their rows counted using the  inspect  command now use the calculated count more effectively - thanks, Kevin Keogh. ( #666 ) \n                 \n                 \n                     --reload  no longer restarts the server if a database file is modified, unless that database was opened immutable mode with  -i . ( #494 ) \n                 \n                 \n                     New  ?_searchmode=raw  option turns off escaping for FTS queries in  ?_search=  allowing full use of SQLite's  FTS5 query syntax . ( #676 )", "sections_fts": 698, "rank": null}
{"rowid": 342, "title": "0.37.1 (2020-03-02)", "content": "Don't attempt to count table rows to display on the index page for databases > 100MB. ( #688 ) \n                 \n                 \n                     Print exceptions if they occur in the write thread rather than silently swallowing them. \n                 \n                 \n                     Handle the possibility of  scope[\"path\"]  being a string rather than bytes \n                 \n                 \n                     Better documentation for the  extra_template_vars(template, database, table, columns, view_name, request, datasette)  plugin hook.", "sections_fts": 698, "rank": null}
{"rowid": 341, "title": "0.38 (2020-03-08)", "content": "The  Docker build  of Datasette now uses SQLite 3.31.1, upgraded from 3.26. ( #695 ) \n                 \n                 \n                     datasette publish cloudrun  now accepts an optional  --memory=2Gi  flag for setting the Cloud Run allocated memory to a value other than the default (256Mi). ( #694 ) \n                 \n                 \n                     Fixed bug where templates that shipped with plugins were sometimes not being correctly loaded. ( #697 )", "sections_fts": 698, "rank": null}
{"rowid": 340, "title": "0.39 (2020-03-24)", "content": "New  base_url  configuration setting for serving up the correct links while running Datasette under a different URL prefix. ( #394 ) \n                 \n                 \n                     New metadata settings  \"sort\"  and  \"sort_desc\"  for setting the default sort order for a table. See  Setting a default sort order . ( #702 ) \n                 \n                 \n                     Sort direction arrow now displays by default on the primary key. This means you only have to click once (not twice) to sort in reverse order. ( #677 ) \n                 \n                 \n                     New  await Request(scope, receive).post_vars()  method for accessing POST form variables. ( #700 ) \n                 \n                 \n                     Plugin hooks  documentation now links to example uses of each plugin. ( #709 )", "sections_fts": 698, "rank": null}
{"rowid": 339, "title": "0.40 (2020-04-21)", "content": "Datasette  Metadata  can now be provided as a YAML file as an optional alternative to JSON. See  Using YAML for metadata . ( #713 ) \n                 \n                 \n                     Removed support for  datasette publish now , which used the the now-retired Zeit Now v1 hosting platform. A new plugin,  datasette-publish-now , can be installed to publish data to Zeit ( now Vercel ) Now v2. ( #710 ) \n                 \n                 \n                     Fixed a bug where the  extra_template_vars(request, view_name)  plugin hook was not receiving the correct  view_name . ( #716 ) \n                 \n                 \n                     Variables added to the template context by the  extra_template_vars()  plugin hook are now shown in the  ?_context=1  debugging mode (see  template_debug ). ( #693 ) \n                 \n                 \n                     Fixed a bug where the \"templates considered\" HTML comment was no longer being displayed. ( #689 ) \n                 \n                 \n                     Fixed a  datasette publish  bug where  --plugin-secret  would over-ride plugin configuration in the provided  metadata.json  file. ( #724 ) \n                 \n                 \n                     Added a new CSS class for customizing the canned query page. ( #727 )", "sections_fts": 698, "rank": null}
{"rowid": 338, "title": "0.41 (2020-05-06)", "content": "You can now create  custom pages  within your Datasette instance using a custom template file. For example, adding a template file called  templates/pages/about.html  will result in a new page being served at  /about  on your instance. See the  custom pages documentation  for full details, including how to return custom HTTP headers, redirects and status codes. ( #648 ) \n             Configuration directory mode  ( #731 ) allows you to define a custom Datasette instance as a directory. So instead of running the following: \n             $ datasette one.db two.db \\\n  --metadata=metadata.json \\\n  --template-dir=templates/ \\\n  --plugins-dir=plugins \\\n  --static css:css \n             You can instead arrange your files in a single directory called  my-project  and run this: \n             $ datasette my-project/ \n             Also in this release: \n             \n                 \n                     New  NOT LIKE  table filter:  ?colname__notlike=expression . ( #750 ) \n                 \n                 \n                     Datasette now has a  pattern portfolio  at  /-/patterns  - e.g.  https://latest.datasette.io/-/patterns . This is a page that shows every Datasette user interface component in one place, to aid core development and people building custom CSS themes. ( #151 ) \n                 \n                 \n                     SQLite  PRAGMA functions  such as  pragma_table_info(tablename)  are now allowed in Datasette SQL queries. ( #761 ) \n                 \n                 \n                     Datasette pages now consistently return a  content-type  of  text/html; charset=utf-8\" . ( #752 ) \n                 \n                 \n                     Datasette now handles an ASGI  raw_path  value of  None , which should allow compatibility with the  Mangum  adapter for running ASGI apps on AWS Lambda. Thanks, Colin Dellow. ( #719 ) \n                 \n                 \n                     Installation documentation now covers how to  Using pipx . ( #756 ) \n                 \n                 \n                     Improved the documentation for  Full-text search . ( #748 )", "sections_fts": 698, "rank": null}
{"rowid": 337, "title": "0.42 (2020-05-08)", "content": "A small release which provides improved internal methods for use in plugins, along with documentation. See  #685 . \n             \n                 \n                     Added documentation for  db.execute() , see  await db.execute(sql, ...) . \n                 \n                 \n                     Renamed  db.execute_against_connection_in_thread()  to  db.execute_fn()  and made it a documented method, see  await db.execute_fn(fn) . \n                 \n                 \n                     New  results.first()  and  results.single_value()  methods, plus documentation for the  Results  class - see  Results .", "sections_fts": 698, "rank": null}
{"rowid": 336, "title": "0.43 (2020-05-28)", "content": "The main focus of this release is a major upgrade to the  register_output_renderer(datasette)  plugin hook, which allows plugins to provide new output formats for Datasette such as  datasette-atom  and  datasette-ics . \n             \n                 \n                     Redesign of  register_output_renderer(datasette)  to provide more context to the render callback and support an optional  \"can_render\"  callback that controls if a suggested link to the output format is provided. ( #581 ,  #770 ) \n                 \n                 \n                     Visually distinguish float and integer columns - useful for figuring out why order-by-column might be returning unexpected results. ( #729 ) \n                 \n                 \n                     The  Request object , which is passed to several plugin hooks, is now documented. ( #706 ) \n                 \n                 \n                     New  metadata.json  option for setting a custom default page size for specific tables and views, see  Setting a custom page size . ( #751 ) \n                 \n                 \n                     Canned queries can now be configured with a default URL fragment hash, useful when working with plugins such as  datasette-vega , see  Additional canned query options . ( #706 ) \n                 \n                 \n                     Fixed a bug in  datasette publish  when running on operating systems where the  /tmp  directory lives in a different volume, using a backport of the Python 3.8  shutil.copytree()  function. ( #744 ) \n                 \n                 \n                     Every plugin hook is now covered by the unit tests, and a new unit test checks that each plugin hook has at least one corresponding test. ( #771 ,  #773 )", "sections_fts": 698, "rank": null}
{"rowid": 335, "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 .", "sections_fts": 698, "rank": null}
{"rowid": 334, "title": "Smaller changes", "content": "New internals documentation for  Request object  and  Response class . ( #706 ) \n                     \n                     \n                         request.url  now respects the  force_https_urls  config setting. closes ( #781 ) \n                     \n                     \n                         request.args.getlist()  returns  []  if missing. Removed  request.raw_args  entirely. ( #774 ) \n                     \n                     \n                         New  datasette.get_database()  method. \n                     \n                     \n                         Added  _  prefix to many private, undocumented methods of the Datasette class. ( #576 ) \n                     \n                     \n                         Removed the  db.get_outbound_foreign_keys()  method which duplicated the behaviour of  db.foreign_keys_for_table() . \n                     \n                     \n                         New  await datasette.permission_allowed()  method. \n                     \n                     \n                         /-/actor  debugging endpoint for viewing the currently authenticated actor. \n                     \n                     \n                         New  request.cookies  property. \n                     \n                     \n                         /-/plugins  endpoint now shows a list of hooks implemented by each plugin, e.g.  https://latest.datasette.io/-/plugins?all=1 \n                     \n                     \n                         request.post_vars()  method no longer discards empty values. \n                     \n                     \n                         New \"params\" canned query key for explicitly setting named parameters, see  Canned query parameters . ( #797 ) \n                     \n                     \n                         request.args  is now a  MultiParams  object. \n                     \n                     \n                         Fixed a bug with the  datasette plugins  command. ( #802 ) \n                     \n                     \n                         Nicer pattern for using  make_app_client()  in tests. ( #395 ) \n                     \n                     \n                         New  request.actor  property. \n                     \n                     \n                         Fixed broken CSS on nested 404 pages. ( #777 ) \n                     \n                     \n                         New  request.url_vars  property. ( #822 ) \n                     \n                     \n                         Fixed a bug with the  python tests/fixtures.py  command for outputting Datasette's testing fixtures database and plugins. ( #804 ) \n                     \n                     \n                         datasette publish heroku  now deploys using Python 3.8.3. \n                     \n                     \n                         Added a warning that the  register_facet_classes()  hook is unstable and may change in the future. ( #830 ) \n                     \n                     \n                         The  {\"$env\": \"ENVIRONMENT_VARIBALE\"}  mechanism (see  Secret configuration values ) now works with variables inside nested lists. ( #837 )", "sections_fts": 698, "rank": null}
{"rowid": 333, "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.", "sections_fts": 698, "rank": null}
{"rowid": 332, "title": "Cookie methods", "content": "Plugins can now use the new  response.set_cookie()  method to set cookies. \n                 A new  request.cookies  method on the :ref:internals_request` can be used to read incoming cookies.", "sections_fts": 698, "rank": null}
{"rowid": 331, "title": "CSRF protection", "content": "Since writable canned queries are built using POST forms, Datasette now ships with  CSRF protection  ( #798 ). This applies automatically to any POST request, which means plugins need to include a  csrftoken  in any POST forms that they render. They can do that like so: \n                 <input type=\"hidden\" name=\"csrftoken\" value=\"{{ csrftoken() }}\">", "sections_fts": 698, "rank": null}
{"rowid": 330, "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.", "sections_fts": 698, "rank": null}
{"rowid": 329, "title": "Flash messages", "content": "Writable canned queries needed a mechanism to let the user know that the query has been successfully executed. The new flash messaging system ( #790 ) allows messages to persist in signed cookies which are then displayed to the user on the next page that they visit. Plugins can use this mechanism to display their own messages, see  .add_message(request, message, type=datasette.INFO)  for details. \n                 You can try out the new messages using the  /-/messages  debug tool, for example at  https://latest.datasette.io/-/messages", "sections_fts": 698, "rank": null}
{"rowid": 328, "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.", "sections_fts": 698, "rank": null}
{"rowid": 327, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 326, "title": "Authentication", "content": "Prior to this release the Datasette ecosystem has treated authentication as exclusively the realm of plugins, most notably through  datasette-auth-github . \n                 0.44 introduces  Authentication and permissions  as core Datasette concepts ( #699 ). This enables different plugins to share responsibility for authenticating requests - you might have one plugin that handles user accounts and another one that allows automated access via API keys, for example. \n                 You'll need to install plugins if you want full user accounts, but default Datasette can now authenticate a single root user with the new  --root  command-line option, which outputs a one-time use URL to  authenticate as a root actor  ( #784 ): \n                 $ datasette fixtures.db --root\nhttp://127.0.0.1:8001/-/auth-token?token=5b632f8cd44b868df625f5a6e2185d88eea5b22237fd3cc8773f107cc4fd6477\nINFO:     Started server process [14973]\nINFO:     Waiting for application startup.\nINFO:     Application startup complete.\nINFO:     Uvicorn running on http://127.0.0.1:8001 (Press CTRL+C to quit) \n                 Plugins can implement new ways of authenticating users using the new  actor_from_request(datasette, request)  hook.", "sections_fts": 698, "rank": null}
{"rowid": 325, "title": "0.44 (2020-06-11)", "content": "See also  Datasette 0.44: The annotated release notes . \n             Authentication and permissions, writable canned queries, flash messages, new plugin hooks and more.", "sections_fts": 698, "rank": null}
{"rowid": 324, "title": "Smaller changes", "content": "Cascading view permissions - so if a user has  view-table  they can view the table page even if they do not have  view-database  or  view-instance . ( #832 ) \n                     \n                     \n                         CSRF protection no longer applies to  Authentication: Bearer token  requests or requests without cookies. ( #835 ) \n                     \n                     \n                         datasette.add_message()  now works inside plugins. ( #864 ) \n                     \n                     \n                         Workaround for \"Too many open files\" error in test runs. ( #846 ) \n                     \n                     \n                         Respect existing  scope[\"actor\"]  if already set by ASGI middleware. ( #854 ) \n                     \n                     \n                         New process for shipping  Alpha and beta releases . ( #807 ) \n                     \n                     \n                         {{ csrftoken() }}  now works when plugins render a template using  datasette.render_template(..., request=request) . ( #863 ) \n                     \n                     \n                         Datasette now creates a single  Request object  and uses it throughout the lifetime of the current HTTP request. ( #870 )", "sections_fts": 698, "rank": null}
{"rowid": 323, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 322, "title": "Better plugin documentation", "content": "The plugin documentation has been re-arranged into four sections, including a brand new section on testing plugins. ( #687 ) \n                 \n                     \n                         Plugins  introduces Datasette's plugin system and describes how to install and configure plugins. \n                     \n                     \n                         Writing plugins  describes how to author plugins, from  one-off single file plugins to packaged plugins that can be published to PyPI. It also describes how to start a plugin using the new  datasette-plugin  cookiecutter template. \n                     \n                     \n                         Plugin hooks  is a full list of detailed documentation for every Datasette plugin hook. \n                     \n                     \n                         Testing plugins  describes how to write tests for Datasette plugins, using  pytest  and  HTTPX .", "sections_fts": 698, "rank": null}
{"rowid": 321, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 320, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 319, "title": "0.45 (2020-07-01)", "content": "See also  Datasette 0.45: The annotated release notes . \n             Magic parameters for canned queries, a log out feature, improved plugin documentation and four new plugin hooks.", "sections_fts": 698, "rank": null}
{"rowid": 318, "title": "0.46 (2020-08-09)", "content": "This release contains a security fix related to authenticated writable canned queries. If you are using this feature you should upgrade as soon as possible. \n             \n             \n                 \n                     Security fix:  CSRF tokens were incorrectly included in read-only canned query forms, which could allow them to be leaked to a sophisticated attacker. See  issue 918  for details. \n                 \n                 \n                     Datasette now supports GraphQL via the new  datasette-graphql  plugin - see  GraphQL in Datasette with the new datasette-graphql plugin . \n                 \n                 \n                     Principle git branch has been renamed from  master  to  main . ( #849 ) \n                 \n                 \n                     New debugging tool:  /-/allow-debug tool  ( demo here ) helps test allow blocks against actors, as described in  Defining permissions with \"allow\" blocks . ( #908 ) \n                 \n                 \n                     New logo for the documentation, and a new project tagline: \"An open source multi-tool for exploring and publishing data\". \n                 \n                 \n                     Whitespace in column values is now respected on display, using  white-space: pre-wrap . ( #896 ) \n                 \n                 \n                     New  await request.post_body()  method for accessing the raw POST body, see  Request object . ( #897 ) \n                 \n                 \n                     Database file downloads now include a  content-length  HTTP header, enabling download progress bars. ( #905 ) \n                 \n                 \n                     File downloads now also correctly set the suggested file name using a  content-disposition  HTTP header. ( #909 ) \n                 \n                 \n                     tests  are now excluded from the Datasette package properly - thanks, abeyerpath. ( #456 ) \n                 \n                 \n                     The Datasette package published to PyPI now includes  sdist  as well as  bdist_wheel . \n                 \n                 \n                     Better titles for canned query pages. ( #887 ) \n                 \n                 \n                     Now only loads Python files from a directory passed using the  --plugins-dir  option - thanks, Amjith Ramanujam. ( #890 ) \n                 \n                 \n                     New documentation section on  Publishing to Vercel .", "sections_fts": 698, "rank": null}
{"rowid": 317, "title": "0.47 (2020-08-11)", "content": "Datasette now has  a GitHub discussions forum  for conversations about the project that go beyond just bug reports and issues. \n                 \n                 \n                     Datasette can now be installed on macOS using Homebrew! Run  brew install simonw/datasette/datasette . See  Using Homebrew . ( #335 ) \n                 \n                 \n                     Two new commands:  datasette install name-of-plugin  and  datasette uninstall name-of-plugin . These are equivalent to  pip install  and  pip uninstall  but automatically run in the same virtual environment as Datasette, so users don't have to figure out where that virtual environment is - useful for installations created using Homebrew or  pipx . See  Installing plugins . ( #925 ) \n                 \n                 \n                     A new command-line option,  datasette --get , accepts a path to a URL within the Datasette instance. It will run that request through Datasette (without starting a web server) and print out the response. See  datasette --get  for an example. ( #926 )", "sections_fts": 698, "rank": null}
{"rowid": 316, "title": "0.47.1 (2020-08-11)", "content": "Fixed a bug where the  sdist  distribution of Datasette was not correctly including the template files. ( #930 )", "sections_fts": 698, "rank": null}
{"rowid": 315, "title": "0.47.2 (2020-08-12)", "content": "Fixed an issue with the Docker image  published to Docker Hub . ( #931 )", "sections_fts": 698, "rank": null}
{"rowid": 314, "title": "0.47.3 (2020-08-15)", "content": "The  datasette --get  command-line mechanism now ensures any plugins using the  startup()  hook are correctly executed. ( #934 )", "sections_fts": 698, "rank": null}
{"rowid": 313, "title": "0.48 (2020-08-16)", "content": "Datasette documentation now lives at  docs.datasette.io . \n                 \n                 \n                     db.is_mutable  property is now documented and tested, see  Database introspection . \n                 \n                 \n                     The  extra_template_vars ,  extra_css_urls ,  extra_js_urls  and  extra_body_script  plugin hooks now all accept the same arguments. See  extra_template_vars(template, database, table, columns, view_name, request, datasette)  for details. ( #939 ) \n                 \n                 \n                     Those hooks now accept a new  columns  argument detailing the table columns that will be rendered on that page. ( #938 ) \n                 \n                 \n                     Fixed bug where plugins calling  db.execute_write_fn()  could hang Datasette if the connection failed. ( #935 ) \n                 \n                 \n                     Fixed bug with the  ?_nl=on  output option and binary data. ( #914 )", "sections_fts": 698, "rank": null}
{"rowid": 312, "title": "0.49 (2020-09-14)", "content": "See also  Datasette 0.49: The annotated release notes . \n             \n                 \n                     Writable canned queries now expose a JSON API, see  JSON API for writable canned queries . ( #880 ) \n                 \n                 \n                     New mechanism for defining page templates with custom path parameters - a template file called  pages/about/{slug}.html  will be used to render any requests to  /about/something . See  Path parameters for pages . ( #944 ) \n                 \n                 \n                     register_output_renderer()  render functions can now return a  Response . ( #953 ) \n                 \n                 \n                     New  --upgrade  option for  datasette install . ( #945 ) \n                 \n                 \n                     New  datasette --pdb  option. ( #962 ) \n                 \n                 \n                     datasette --get  exit code now reflects the internal HTTP status code. ( #947 ) \n                 \n                 \n                     New  raise_404()  template function for returning 404 errors. ( #964 ) \n                 \n                 \n                     datasette publish heroku  now deploys using Python 3.8.5 \n                 \n                 \n                     Upgraded  CodeMirror  to 5.57.0. ( #948 ) \n                 \n                 \n                     Upgraded code style to Black 20.8b1. ( #958 ) \n                 \n                 \n                     Fixed bug where selected facets were not correctly persisted in hidden form fields on the table page. ( #963 ) \n                 \n                 \n                     Renamed the default error template from  500.html  to  error.html . \n                 \n                 \n                     Custom error pages are now documented, see  Custom error pages . ( #965 )", "sections_fts": 698, "rank": null}
{"rowid": 311, "title": "0.49.1 (2020-09-15)", "content": "Fixed a bug with writable canned queries that use magic parameters but accept no non-magic arguments. ( #967 )", "sections_fts": 698, "rank": null}
{"rowid": 310, "title": "0.50 (2020-10-09)", "content": "The key new feature in this release is the  column actions  menu on the table page ( #891 ). This can be used to sort a column in ascending or descending order, facet data by that column or filter the table to just rows that have a value for that column. \n             Plugin authors can use the new  datasette.client  object to make internal HTTP requests from their plugins, allowing them to make use of Datasette's JSON API. ( #943 ) \n             New  Deploying Datasette  documentation with guides for deploying Datasette on a Linux server  using systemd  or to hosting providers  that support buildpacks . ( #514 ,  #997 ) \n             Other improvements in this release: \n             \n                 \n                     Publishing to Google Cloud Run  documentation now covers Google Cloud SDK options. Thanks, Geoffrey Hing. ( #995 ) \n                 \n                 \n                     New  datasette -o  option which opens your browser as soon as Datasette starts up. ( #970 ) \n                 \n                 \n                     Datasette now sets  sqlite3.enable_callback_tracebacks(True)  so that errors in custom SQL functions will display tracebacks. ( #891 ) \n                 \n                 \n                     Fixed two rendering bugs with column headers in portrait mobile view. ( #978 ,  #980 ) \n                 \n                 \n                     New  db.table_column_details(table)  introspection method for retrieving full details of the columns in a specific table, see  Database introspection . \n                 \n                 \n                     Fixed a routing bug with custom page wildcard templates. ( #996 ) \n                 \n                 \n                     datasette publish heroku  now deploys using Python 3.8.6. \n                 \n                 \n                     New  datasette publish heroku --tar=  option. ( #969 ) \n                 \n                 \n                     OPTIONS  requests against HTML pages no longer return a 500 error. ( #1001 ) \n                 \n                 \n                     Datasette now supports Python 3.9. \n                 \n             \n             See also  Datasette 0.50: The annotated release notes .", "sections_fts": 698, "rank": null}
{"rowid": 309, "title": "0.50.1 (2020-10-09)", "content": "Fixed a bug introduced in 0.50 where the export as JSON/CSV links on the table, row and query pages were broken. ( #1010 )", "sections_fts": 698, "rank": null}
{"rowid": 308, "title": "0.50.2 (2020-10-09)", "content": "Fixed another bug introduced in 0.50 where column header links on the table page were broken. ( #1011 )", "sections_fts": 698, "rank": null}
{"rowid": 307, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 306, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 305, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 304, "title": "Binary data", "content": "SQLite tables can contain binary data in  BLOB  columns. Datasette now provides links for users to download this data directly from Datasette, and uses those links to make binary data available from CSV exports. See  Binary data  for more details. ( #1036  and  #1034 ).", "sections_fts": 698, "rank": null}
{"rowid": 303, "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.", "sections_fts": 698, "rank": null}
{"rowid": 302, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 301, "title": "0.51 (2020-10-31)", "content": "A new visual design, plugin hooks for adding navigation options, better handling of binary data, URL building utility methods and better support for running Datasette behind a proxy.", "sections_fts": 698, "rank": null}
{"rowid": 300, "title": "0.51.1 (2020-10-31)", "content": "Improvements to the new  Binary data  documentation page.", "sections_fts": 698, "rank": null}
{"rowid": 299, "title": "0.52 (2020-11-28)", "content": "This release includes a number of changes relating to an internal rebranding effort: Datasette's  configuration  mechanism (things like  datasette --config default_page_size:10 ) has been renamed to  settings . \n             \n                 \n                     New  --setting default_page_size 10  option as a replacement for  --config default_page_size:10  (note the lack of a colon). The  --config  option is deprecated but will continue working until Datasette 1.0. ( #992 ) \n                 \n                 \n                     The  /-/config  introspection page is now  /-/settings , and the previous page redirects to the new one. ( #1103 ) \n                 \n                 \n                     The  config.json  file in  Configuration directory mode  is now called  settings.json . ( #1104 ) \n                 \n                 \n                     The undocumented  datasette.config()  internal method has been replaced by a documented  .setting(key)  method. ( #1107 ) \n                 \n             \n             Also in this release: \n             \n                 \n                     New plugin hook:  database_actions(datasette, actor, database, request) , which adds menu items to a new cog menu shown at the top of the database page. ( #1077 ) \n                 \n                 \n                     datasette publish cloudrun  has a new  --apt-get-install  option that can be used to install additional Ubuntu packages as part of the deployment. This is useful for deploying the new  datasette-ripgrep plugin . ( #1110 ) \n                 \n                 \n                     Swept the documentation to remove words that minimize involved difficulty. ( #1089 ) \n                 \n             \n             And some bug fixes: \n             \n                 \n                     Foreign keys linking to rows with blank label columns now display as a hyphen, allowing those links to be clicked. ( #1086 ) \n                 \n                 \n                     Fixed bug where row pages could sometimes 500 if the underlying queries exceeded a time limit. ( #1088 ) \n                 \n                 \n                     Fixed a bug where the table action menu could appear partially obscured by the edge of the page. ( #1084 )", "sections_fts": 698, "rank": null}
{"rowid": 298, "title": "0.52.1 (2020-11-29)", "content": "Documentation on  Testing plugins  now recommends using  datasette.client . ( #1102 ) \n                 \n                 \n                     Fix bug where compound foreign keys produced broken links. ( #1098 ) \n                 \n                 \n                     datasette --load-module=spatialite  now also checks for  /usr/local/lib/mod_spatialite.so . Thanks, Dan Peterson. ( #1114 )", "sections_fts": 698, "rank": null}
{"rowid": 297, "title": "0.52.2 (2020-12-02)", "content": "Generated columns from SQLite 3.31.0 or higher are now correctly displayed. ( #1116 ) \n                 \n                 \n                     Error message if you attempt to open a SpatiaLite database now suggests using  --load-extension=spatialite  if it detects that the extension is available in a common location. ( #1115 ) \n                 \n                 \n                     OPTIONS  requests against the  /database  page no longer raise a 500 error. ( #1100 ) \n                 \n                 \n                     Databases larger than 32MB that are published to Cloud Run can now be downloaded. ( #749 ) \n                 \n                 \n                     Fix for misaligned cog icon on table and database pages. Thanks, Abdussamet Ko\u00e7ak. ( #1121 )", "sections_fts": 698, "rank": null}
{"rowid": 296, "title": "0.52.3 (2020-12-03)", "content": "Fixed bug where static assets would 404 for Datasette installed on ARM Amazon Linux. ( #1124 )", "sections_fts": 698, "rank": null}
{"rowid": 295, "title": "0.52.4 (2020-12-05)", "content": "Show  pysqlite3  version on  /-/versions , if installed. ( #1125 ) \n                 \n                 \n                     Errors output by Datasette (e.g. for invalid SQL queries) now go to  stderr , not  stdout . ( #1131 ) \n                 \n                 \n                     Fix for a startup error on windows caused by unnecessary  from os import EX_CANTCREAT  - thanks, Abdussamet Ko\u00e7ak.  ( #1094 )", "sections_fts": 698, "rank": null}
{"rowid": 294, "title": "0.52.5 (2020-12-09)", "content": "Fix for error caused by combining the  _searchmode=raw  and  ?_search_COLUMN  parameters. ( #1134 )", "sections_fts": 698, "rank": null}
{"rowid": 293, "title": "0.53 (2020-12-10)", "content": "Datasette has an official project website now, at  https://datasette.io/ . This release mainly updates the documentation to reflect the new site. \n             \n                 \n                     New  ?column__arraynotcontains=  table filter. ( #1132 ) \n                 \n                 \n                     datasette serve  has a new  --create  option, which will create blank database files if they do not already exist rather than exiting with an error. ( #1135 ) \n                 \n                 \n                     New  ?_header=off  option for CSV export which omits the CSV header row,  documented here . ( #1133 ) \n                 \n                 \n                     \"Powered by Datasette\" link in the footer now links to  https://datasette.io/ . ( #1138 ) \n                 \n                 \n                     Project news no longer lives in the README - it can now be found at  https://datasette.io/news . ( #1137 )", "sections_fts": 698, "rank": null}
{"rowid": 292, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 291, "title": "Code formatting with Black and Prettier", "content": "Datasette adopted  Black  for opinionated Python code formatting in June 2019. Datasette now also embraces  Prettier  for JavaScript formatting, which like Black is enforced by tests in continuous integration. Instructions for using these two tools can be found in the new section on  Code formatting  in the contributors documentation. ( #1167 )", "sections_fts": 698, "rank": null}
{"rowid": 290, "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.", "sections_fts": 698, "rank": null}
{"rowid": 289, "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.", "sections_fts": 698, "rank": null}
{"rowid": 288, "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.", "sections_fts": 698, "rank": null}
{"rowid": 287, "title": "0.54 (2021-01-25)", "content": "The two big new features in this release are the  _internal  SQLite in-memory database storing details of all connected databases and tables, and support for JavaScript modules in plugins and additional scripts. \n             For additional commentary on this release, see  Datasette 0.54, the annotated release notes .", "sections_fts": 698, "rank": null}
{"rowid": 286, "title": "0.54.1 (2021-02-02)", "content": "Fixed a bug where  ?_search=  and  ?_sort=  parameters were incorrectly duplicated when the filter form on the table page was re-submitted. ( #1214 )", "sections_fts": 698, "rank": null}
{"rowid": 285, "title": "0.55 (2021-02-18)", "content": "Support for cross-database SQL queries and built-in support for serving via HTTPS. \n             \n                 \n                     The new  --crossdb  command-line option causes Datasette to attach up to ten database files to the same  /_memory  database connection. This enables cross-database SQL queries, including the ability to use joins and unions to combine data from tables that exist in different database files. See  Cross-database queries  for details. ( #283 ) \n                 \n                 \n                     --ssl-keyfile  and  --ssl-certfile  options can be used to specify a TLS certificate, allowing Datasette to serve traffic over  https://  without needing to run it behind a separate proxy. ( #1221 ) \n                 \n                 \n                     The  /:memory:  page has been renamed (and redirected) to  /_memory  for consistency with the new  /_internal  database introduced in Datasette 0.54. ( #1205 ) \n                 \n                 \n                     Added plugin testing documentation on  Using pdb for errors thrown inside Datasette . ( #1207 ) \n                 \n                 \n                     The  official Datasette Docker image  now uses Python 3.7.10, applying  the latest security fix  for that Python version. ( #1235 )", "sections_fts": 698, "rank": null}
{"rowid": 284, "title": "0.56 (2021-03-28)", "content": "Documentation improvements, bug fixes and support for SpatiaLite 5. \n             \n                 \n                     The SQL editor can now be resized by dragging a handle. ( #1236 ) \n                 \n                 \n                     Fixed a bug with JSON faceting and the  __arraycontains  filter caused by tables with spaces in their names. ( #1239 ) \n                 \n                 \n                     Upgraded  httpx  dependency. ( #1005 ) \n                 \n                 \n                     JSON faceting is now suggested even if a column contains blank strings. ( #1246 ) \n                 \n                 \n                     New  datasette.add_memory_database()  method. ( #1247 ) \n                 \n                 \n                     The  Response.asgi_send()  method is now documented. ( #1266 ) \n                 \n                 \n                     The official Datasette Docker image now bundles SpatiaLite version 5. ( #1278 ) \n                 \n                 \n                     Fixed a  no such table: pragma_database_list  bug when running Datasette against SQLite versions prior to SQLite 3.16.0. ( #1276 ) \n                 \n                 \n                     HTML lists displayed in table cells are now styled correctly. Thanks, Bob Whitelock. ( #1141 ,  #1252 ) \n                 \n                 \n                     Configuration directory mode now correctly serves immutable databases that are listed in  inspect-data.json . Thanks Campbell Allen and Frankie Robertson. ( #1031 ,  #1229 )", "sections_fts": 698, "rank": null}
{"rowid": 283, "title": "0.56.1 (2021-06-05)", "content": "This release fixes a  reflected cross-site scripting  security hole with the  ?_trace=1  feature. You should upgrade to this version, or to Datasette 0.57, as soon as possible. ( #1360 )", "sections_fts": 698, "rank": null}
{"rowid": 282, "title": "Bug fixes and other improvements", "content": "Custom pages  now work correctly when combined with the  base_url  setting. ( #1238 ) \n                     \n                     \n                         Fixed intermittent error displaying the index page when the user did not have permission to access one of the tables. Thanks, Guy Freeman. ( #1305 ) \n                     \n                     \n                         Columns with the name \"Link\" are no longer incorrectly displayed in bold. ( #1308 ) \n                     \n                     \n                         Fixed error caused by tables with a single quote in their names. ( #1257 ) \n                     \n                     \n                         Updated dependencies:  pytest-asyncio ,  Black ,  jinja2 ,  aiofiles ,  click , and  itsdangerous . \n                     \n                     \n                         The official Datasette Docker image now supports  apt-get install . ( #1320 ) \n                     \n                     \n                         The Heroku runtime used by  datasette publish heroku  is now  python-3.8.10 .", "sections_fts": 698, "rank": null}
{"rowid": 281, "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 )", "sections_fts": 698, "rank": null}
{"rowid": 280, "title": "0.57 (2021-06-05)", "content": "This release fixes a  reflected cross-site scripting  security hole with the  ?_trace=1  feature. You should upgrade to this version, or to Datasette 0.56.1, as soon as possible. ( #1360 ) \n             \n             In addition to the security fix, this release includes  ?_col=  and  ?_nocol=  options for controlling which columns are displayed for a table,  ?_facet_size=  for increasing the number of facet results returned, re-display of your SQL query should an error occur and numerous bug fixes.", "sections_fts": 698, "rank": null}
{"rowid": 279, "title": "0.57.1 (2021-06-08)", "content": "Fixed visual display glitch with global navigation menu. ( #1367 ) \n                 \n                 \n                     No longer truncates the list of table columns displayed on the  /database  page. ( #1364 )", "sections_fts": 698, "rank": null}