{"rowid": 1, "title": "Running SQL queries", "content": "Datasette treats SQLite database files as read-only and immutable. This means it is not possible to execute INSERT or UPDATE statements using Datasette, which allows us to expose SELECT statements to the outside world without needing to worry about SQL injection attacks. \n         The easiest way to execute custom SQL against Datasette is through the web UI. The database index page includes a SQL editor that lets you run any SELECT query you like. You can also construct queries using the filter interface on the tables page, then click \"View and edit SQL\" to open that query in the custom SQL editor. \n         Note that this interface is only available if the  execute-sql  permission is allowed. See  Controlling the ability to execute arbitrary SQL . \n         Any Datasette SQL query is reflected in the URL of the page, allowing you to bookmark them, share them with others and navigate through previous queries using your browser back button. \n         You can also retrieve the results of any query as JSON by adding  .json  to the base URL.", "sections_fts": 124, "rank": null}
{"rowid": 2, "title": "Named parameters", "content": "Datasette has special support for SQLite named parameters. Consider a SQL query like this: \n             select * from Street_Tree_List\nwhere \"PermitNotes\" like :notes\nand \"qSpecies\" = :species \n             If you execute this query using the custom query editor, Datasette will extract the two named parameters and use them to construct form fields for you to provide values. \n             You can also provide values for these fields by constructing a URL: \n             /mydatabase?sql=select...&species=44 \n             SQLite string escaping rules will be applied to values passed using named parameters - they will be wrapped in quotes and their content will be correctly escaped. \n             Values from named parameters are treated as SQLite strings. If you need to perform numeric comparisons on them you should cast them to an integer or float first using  cast(:name as integer)  or  cast(:name as real) , for example: \n             select * from Street_Tree_List\nwhere latitude > cast(:min_latitude as real)\nand latitude < cast(:max_latitude as real) \n             Datasette disallows custom SQL queries containing the string PRAGMA (with a small number  of exceptions ) as SQLite pragma statements can be used to change database settings at runtime. If you need to include the string \"pragma\" in a query you can do so safely using a named parameter.", "sections_fts": 124, "rank": null}
{"rowid": 3, "title": "Views", "content": "If you want to bundle some pre-written SQL queries with your Datasette-hosted database you can do so in two ways. The first is to include SQL views in your database - Datasette will then list those views on your database index page. \n             The quickest way to create views is with the SQLite command-line interface: \n             sqlite3 sf-trees.db \n             SQLite version 3.19.3 2017-06-27 16:48:08\nEnter \".help\" for usage hints.\nsqlite> CREATE VIEW demo_view AS select qSpecies from Street_Tree_List;\n<CTRL+D> \n             You can also use the  sqlite-utils  tool to  create a view : \n             sqlite-utils create-view sf-trees.db demo_view \"select qSpecies from Street_Tree_List\"", "sections_fts": 124, "rank": null}
{"rowid": 4, "title": "Canned queries", "content": "As an alternative to adding views to your database, you can define canned queries inside your  datasette.yaml  file. Here's an example: \n             [[[cog\nfrom metadata_doc import config_example, config_example\nconfig_example(cog, {\n    \"databases\": {\n       \"sf-trees\": {\n           \"queries\": {\n               \"just_species\": {\n                   \"sql\": \"select qSpecies from Street_Tree_List\"\n               }\n           }\n       }\n    }\n}) \n             ]]] \n             [[[end]]] \n             Then run Datasette like this: \n             datasette sf-trees.db -m metadata.json \n             Each canned query will be listed on the database index page, and will also get its own URL at: \n             /database-name/canned-query-name \n             For the above example, that URL would be: \n             /sf-trees/just_species \n             You can optionally include  \"title\"  and  \"description\"  keys to show a title and description on the canned query page. As with regular table metadata you can alternatively specify  \"description_html\"  to have your description rendered as HTML (rather than having HTML special characters escaped).", "sections_fts": 124, "rank": null}
{"rowid": 5, "title": "Canned query parameters", "content": "Canned queries support named parameters, so if you include those in the SQL you will then be able to enter them using the form fields on the canned query page or by adding them to the URL. This means canned queries can be used to create custom JSON APIs based on a carefully designed SQL statement. \n                 Here's an example of a canned query with a named parameter: \n                 select neighborhood, facet_cities.name, state\nfrom facetable\n  join facet_cities on facetable.city_id = facet_cities.id\nwhere neighborhood like '%' || :text || '%'\norder by neighborhood; \n                 In the canned query configuration looks like this: \n                 [[[cog\nconfig_example(cog, \"\"\"\ndatabases:\n  fixtures:\n    queries:\n      neighborhood_search:\n        title: Search neighborhoods\n        sql: |-\n          select neighborhood, facet_cities.name, state\n          from facetable\n            join facet_cities on facetable.city_id = facet_cities.id\n          where neighborhood like '%' || :text || '%'\n          order by neighborhood\n\"\"\") \n                 ]]] \n                 [[[end]]] \n                 Note that we are using SQLite string concatenation here - the  ||  operator - to add wildcard  %  characters to the string provided by the user. \n                 You can try this canned query out here:\n                     https://latest.datasette.io/fixtures/neighborhood_search?text=town \n                 In this example the  :text  named parameter is automatically extracted from the query using a regular expression. \n                 You can alternatively provide an explicit list of named parameters using the  \"params\"  key, like this: \n                 [[[cog\nconfig_example(cog, \"\"\"\ndatabases:\n  fixtures:\n    queries:\n      neighborhood_search:\n        title: Search neighborhoods\n        params:\n        - text\n        sql: |-\n          select neighborhood, facet_cities.name, state\n          from facetable\n            join facet_cities on facetable.city_id = facet_cities.id\n          where neighborhood like '%' || :text || '%'\n          order by neighborhood\n\"\"\") \n                 ]]] \n                 [[[end]]]", "sections_fts": 124, "rank": null}
{"rowid": 6, "title": "Additional canned query options", "content": "Additional options can be specified for canned queries in the YAML or JSON configuration.", "sections_fts": 124, "rank": null}
{"rowid": 7, "title": "hide_sql", "content": "Canned queries default to displaying their SQL query at the top of the page. If the query is extremely long you may want to hide it by default, with a \"show\" link that can be used to make it visible. \n                     Add the  \"hide_sql\": true  option to hide the SQL query by default.", "sections_fts": 124, "rank": null}
{"rowid": 8, "title": "fragment", "content": "Some plugins, such as  datasette-vega , can be configured by including additional data in the fragment hash of the URL - the bit that comes after a  #  symbol. \n                     You can set a default fragment hash that will be included in the link to the canned query from the database index page using the  \"fragment\"  key. \n                     This example demonstrates both  fragment  and  hide_sql : \n                     [[[cog\nconfig_example(cog, \"\"\"\ndatabases:\n  fixtures:\n    queries:\n      neighborhood_search:\n        fragment: fragment-goes-here\n        hide_sql: true\n        sql: |-\n          select neighborhood, facet_cities.name, state\n          from facetable join facet_cities on facetable.city_id = facet_cities.id\n          where neighborhood like '%' || :text || '%' order by neighborhood;\n\"\"\") \n                     ]]] \n                     [[[end]]] \n                     See here  for a demo of this in action.", "sections_fts": 124, "rank": null}
{"rowid": 9, "title": "Writable canned queries", "content": "Canned queries by default are read-only. You can use the  \"write\": true  key to indicate that a canned query can write to the database. \n                 See  Access to specific canned queries  for details on how to add permission checks to canned queries, using the  \"allow\"  key. \n                 [[[cog\nconfig_example(cog, {\n    \"databases\": {\n        \"mydatabase\": {\n            \"queries\": {\n                \"add_name\": {\n                    \"sql\": \"INSERT INTO names (name) VALUES (:name)\",\n                    \"write\": True\n                }\n            }\n        }\n    }\n}) \n                 ]]] \n                 [[[end]]] \n                 This configuration will create a page at  /mydatabase/add_name  displaying a form with a  name  field. Submitting that form will execute the configured  INSERT  query. \n                 You can customize how Datasette represents success and errors using the following optional properties: \n                 \n                     \n                         on_success_message  - the message shown when a query is successful \n                     \n                     \n                         on_success_message_sql  - alternative to  on_success_message : a SQL query that should be executed to generate the message \n                     \n                     \n                         on_success_redirect  - the path or URL the user is redirected to on success \n                     \n                     \n                         on_error_message  - the message shown when a query throws an error \n                     \n                     \n                         on_error_redirect  - the path or URL the user is redirected to on error \n                     \n                 \n                 For example: \n                 [[[cog\nconfig_example(cog, {\n    \"databases\": {\n        \"mydatabase\": {\n            \"queries\": {\n                \"add_name\": {\n                    \"sql\": \"INSERT INTO names (name) VALUES (:name)\",\n                    \"params\": [\"name\"],\n                    \"write\": True,\n                    \"on_success_message_sql\": \"select 'Name inserted: ' || :name\",\n                    \"on_success_redirect\": \"/mydatabase/names\",\n                    \"on_error_message\": \"Name insert failed\",\n                    \"on_error_redirect\": \"/mydatabase\",\n                }\n            }\n        }\n    }\n}) \n                 ]]] \n                 [[[end]]] \n                 You can use  \"params\"  to explicitly list the named parameters that should be displayed as form fields - otherwise they will be automatically detected.  \"params\"  is not necessary in the above example, since without it  \"name\"  would be automatically detected from the query. \n                 You can pre-populate form fields when the page first loads using a query string, e.g.  /mydatabase/add_name?name=Prepopulated . The user will have to submit the form to execute the query. \n                 If you specify a query in  \"on_success_message_sql\" , that query will be executed after the main query. The first column of the first row return by that query will be displayed as a success message. Named parameters from the main query will be made available to the success message query as well.", "sections_fts": 124, "rank": null}
{"rowid": 10, "title": "Magic parameters", "content": "Named parameters that start with an underscore are special: they can be used to automatically add values created by Datasette that are not contained in the incoming form fields or query string. \n                 These magic parameters are only supported for canned queries: to avoid security issues (such as queries that extract the user's private cookies) they are not available to SQL that is executed by the user as a custom SQL query. \n                 Available magic parameters are: \n                 \n                     \n                         _actor_*  - e.g.  _actor_id ,  _actor_name \n                         \n                             Fields from the currently authenticated  Actors . \n                         \n                     \n                     \n                         _header_*  - e.g.  _header_user_agent \n                         \n                             Header from the incoming HTTP request. The key should be in lower case and with hyphens converted to underscores e.g.  _header_user_agent  or  _header_accept_language . \n                         \n                     \n                     \n                         _cookie_*  - e.g.  _cookie_lang \n                         \n                             The value of the incoming cookie of that name. \n                         \n                     \n                     \n                         _now_epoch \n                         \n                             The number of seconds since the Unix epoch. \n                         \n                     \n                     \n                         _now_date_utc \n                         \n                             The date in UTC, e.g.  2020-06-01 \n                         \n                     \n                     \n                         _now_datetime_utc \n                         \n                             The ISO 8601 datetime in UTC, e.g.  2020-06-24T18:01:07Z \n                         \n                     \n                     \n                         _random_chars_*  - e.g.  _random_chars_128 \n                         \n                             A random string of characters of the specified length. \n                         \n                     \n                 \n                 Here's an example configuration that adds a message from the authenticated user, storing various pieces of additional metadata using magic parameters: \n                 [[[cog\nconfig_example(cog, \"\"\"\ndatabases:\n  mydatabase:\n    queries:\n      add_message:\n        allow:\n          id: \"*\"\n        sql: |-\n          INSERT INTO messages (\n            user_id, message, datetime\n          ) VALUES (\n            :_actor_id, :message, :_now_datetime_utc\n          )\n        write: true\n\"\"\") \n                 ]]] \n                 [[[end]]] \n                 The form presented at  /mydatabase/add_message  will have just a field for  message  - the other parameters will be populated by the magic parameter mechanism. \n                 Additional custom magic parameters can be added by plugins using the  register_magic_parameters(datasette)  hook.", "sections_fts": 124, "rank": null}
{"rowid": 11, "title": "JSON API for writable canned queries", "content": "Writable canned queries can also be accessed using a JSON API. You can POST data to them using JSON, and you can request that their response is returned to you as JSON. \n                 To submit JSON to a writable canned query, encode key/value parameters as a JSON document: \n                 POST /mydatabase/add_message\n\n{\"message\": \"Message goes here\"} \n                 You can also continue to submit data using regular form encoding, like so: \n                 POST /mydatabase/add_message\n\nmessage=Message+goes+here \n                 There are three options for specifying that you would like the response to your request to return JSON data, as opposed to an HTTP redirect to another page. \n                 \n                     \n                         Set an  Accept: application/json  header on your request \n                     \n                     \n                         Include  ?_json=1  in the URL that you POST to \n                     \n                     \n                         Include  \"_json\": 1  in your JSON body, or  &_json=1  in your form encoded body \n                     \n                 \n                 The JSON response will look like this: \n                 {\n    \"ok\": true,\n    \"message\": \"Query executed, 1 row affected\",\n    \"redirect\": \"/data/add_name\"\n} \n                 The  \"message\"  and  \"redirect\"  values here will take into account  on_success_message ,  on_success_message_sql ,   on_success_redirect ,  on_error_message  and  on_error_redirect , if they have been set.", "sections_fts": 124, "rank": null}
{"rowid": 12, "title": "Pagination", "content": "Datasette's default table pagination is designed to be extremely efficient. SQL OFFSET/LIMIT pagination can have a significant performance penalty once you get into multiple thousands of rows, as each page still requires the database to scan through every preceding row to find the correct offset. \n             When paginating through tables, Datasette instead orders the rows in the table by their primary key and performs a WHERE clause against the last seen primary key for the previous page. For example: \n             select rowid, * from Tree_List where rowid > 200 order by rowid limit 101 \n             This represents page three for this particular table, with a page size of 100. \n             Note that we request 101 items in the limit clause rather than 100. This allows us to detect if we are on the last page of the results: if the query returns less than 101 rows we know we have reached the end of the pagination set. Datasette will only return the first 100 rows - the 101st is used purely to detect if there should be another page. \n             Since the where clause acts against the index on the primary key, the query is extremely fast even for records that are a long way into the overall pagination set.", "sections_fts": 124, "rank": null}
{"rowid": 13, "title": "Cross-database queries", "content": "SQLite has the ability to run queries that join across multiple databases. Up to ten databases can be attached to a single SQLite connection and queried together. \n             Datasette can execute joins across multiple databases if it is started with the  --crossdb  option: \n             datasette fixtures.db extra_database.db --crossdb \n             If it is started in this way, the  /_memory  page can be used to execute queries that join across multiple databases. \n             References to tables in attached databases should be preceded by the database name and a period. \n             For example, this query will show a list of tables across both of the above databases: \n             select\n  'fixtures' as database, *\nfrom\n  [fixtures].sqlite_master\nunion\nselect\n  'extra_database' as database, *\nfrom\n  [extra_database].sqlite_master \n             Try that out here .", "sections_fts": 124, "rank": null}
{"rowid": 14, "title": "Changelog", "content": "", "sections_fts": 124, "rank": null}
{"rowid": 15, "title": "1.0a19 (2025-04-21)", "content": "Tiny cosmetic bug fix for mobile display of table rows. ( #2479 )", "sections_fts": 124, "rank": null}
{"rowid": 16, "title": "1.0a18 (2025-04-16)", "content": "Fix for incorrect foreign key references in the internal database schema. ( #2466 ) \n                 \n                 \n                     The  prepare_connection()  hook no longer runs for the internal database. ( #2468 ) \n                 \n                 \n                     Fixed bug where  link:  HTTP headers used invalid syntax. ( #2470 ) \n                 \n                 \n                     No longer tested against Python 3.8. Now tests against Python 3.13. \n                 \n                 \n                     FTS tables are now hidden by default if they correspond to a content table. ( #2477 ) \n                 \n                 \n                     Fixed bug with foreign key links to rows in databases with filenames containing a special character. Thanks,  Jack Stratton . ( #2476 )", "sections_fts": 124, "rank": null}
{"rowid": 17, "title": "1.0a17 (2025-02-06)", "content": "DATASETTE_SSL_KEYFILE  and  DATASETTE_SSL_CERTFILE  environment variables as alternatives to  --ssl-keyfile  and  --ssl-certfile . Thanks, Alex Garcia. ( #2422 ) \n                 \n                 \n                     SQLITE_EXTENSIONS  environment variable has been renamed to  DATASETTE_LOAD_EXTENSION . ( #2424 ) \n                 \n                 \n                     datasette serve  environment variables are now  documented here . \n                 \n                 \n                     The  register_magic_parameters(datasette)  plugin hook can now register async functions. ( #2441 ) \n                 \n                 \n                     Datasette is now tested against Python 3.13. \n                 \n                 \n                     Breadcrumbs on database and table pages now include a consistent self-link for resetting query string parameters. ( #2454 ) \n                 \n                 \n                     Fixed issue where Datasette could crash on  metadata.json  with nested values. ( #2455 ) \n                 \n                 \n                     New internal methods  datasette.set_actor_cookie()  and  datasette.delete_actor_cookie() ,  described here . ( #1690 ) \n                 \n                 \n                     /-/permissions  page now shows a list of all permissions registered by plugins. ( #1943 ) \n                 \n                 \n                     If a table has a single unique text column Datasette now detects that as the foreign key label for that table. ( #2458 ) \n                 \n                 \n                     The  /-/permissions  page now includes options for filtering or exclude permission checks recorded against the current user. ( #2460 ) \n                 \n                 \n                     Fixed a bug where replacing a database with a new one with the same name did not pick up the new database correctly. ( #2465 )", "sections_fts": 124, "rank": null}
{"rowid": 18, "title": "0.65.1 (2024-11-28)", "content": "Fixed bug with upgraded HTTPX 0.28.0 dependency. ( #2443 )", "sections_fts": 124, "rank": null}
{"rowid": 19, "title": "0.65 (2024-10-07)", "content": "Upgrade for compatibility with Python 3.13 (by vendoring Pint dependency). ( #2434 ) \n                 \n                 \n                     Dropped support for Python 3.8.", "sections_fts": 124, "rank": null}
{"rowid": 20, "title": "1.0a16 (2024-09-05)", "content": "This release focuses on performance, in particular against large tables, and introduces some minor breaking changes for CSS styling in Datasette plugins. \n             \n                 \n                     Removed the unit conversions feature and its dependency, Pint. This means Datasette is now compatible with the upcoming Python 3.13. ( #2400 ,  #2320 ) \n                 \n                 \n                     The  datasette --pdb  option now uses the  ipdb  debugger if it is installed. You can install it using  datasette install ipdb . Thanks,  Tiago Ilieve . ( #2342 ) \n                 \n                 \n                     Fixed a confusing error that occurred if  metadata.json  contained nested objects. ( #2403 ) \n                 \n                 \n                     Fixed a bug with  ?_trace=1  where it returned a blank page if the response was larger than 256KB. ( #2404 ) \n                 \n                 \n                     Tracing mechanism now also displays SQL queries that returned errors or ran out of time.  datasette-pretty-traces 0.5  includes support for displaying this new type of trace. ( #2405 ) \n                 \n                 \n                     Fixed a text spacing with table descriptions on the homepage. ( #2399 ) \n                 \n                 \n                     \n                         \n                             Performance improvements for large tables: \n                             \n                                 \n                                     \n                                         Suggested facets now only consider the first 1000 rows. ( #2406 ) \n                                     \n                                     \n                                         Improved performance of date facet suggestion against large tables. ( #2407 ) \n                                     \n                                     \n                                         Row counts stop at 10,000 rows when listing tables. ( #2398 ) \n                                     \n                                     \n                                         On table page the count stops at 10,000 rows too, with a \"count all\" button to execute the full count. ( #2408 ) \n                                     \n                                 \n                             \n                         \n                     \n                 \n                 \n                     New  .dicts()  internal method on  Results  that returns a list of dictionaries representing the results from a SQL query: ( #2414 ) \n                     rows = (await db.execute(\"select * from t\")).dicts() \n                 \n                 \n                     Default Datasette core CSS that styles inputs and buttons now requires a class of  \"core\"  on the element or a containing element, for example  <form class=\"core\"> . ( #2415 ) \n                 \n                 \n                     Similarly, default table styles now only apply to  <table class=\"rows-and-columns\"> . ( #2420 )", "sections_fts": 124, "rank": null}
{"rowid": 21, "title": "1.0a15 (2024-08-15)", "content": "Datasette now defaults to hiding SQLite \"shadow\" tables, as seen in extensions such as SQLite FTS and  sqlite-vec . Virtual tables that it makes sense to display, such as FTS core tables, are no longer hidden. Thanks,  Alex Garcia . ( #2296 ) \n                 \n                 \n                     Fixed bug where running Datasette with one or more  -s/--setting  options could over-ride settings that were present in  datasette.yml . ( #2389 ) \n                 \n                 \n                     The Datasette homepage is now duplicated at  /-/ , using the default  index.html  template. This ensures that the information on that page is still accessible even if the Datasette homepage has been customized using a custom  index.html  template, for example on sites like  datasette.io . ( #2393 ) \n                 \n                 \n                     Failed CSRF checks now display a more user-friendly error page. ( #2390 ) \n                 \n                 \n                     Fixed a bug where the  json1  extension was not correctly detected on the  /-/versions  page. Thanks,  Seb Bacon . ( #2326 ) \n                 \n                 \n                     Fixed a bug where the Datasette write API did not correctly accept  Content-Type: application/json; charset=utf-8 . ( #2384 ) \n                 \n                 \n                     Fixed a bug where Datasette would fail to start if  metadata.yml  contained a  queries  block. ( #2386 )", "sections_fts": 124, "rank": null}
{"rowid": 22, "title": "1.0a14 (2024-08-05)", "content": "This alpha introduces significant changes to Datasette's  Metadata  system, some of which represent breaking changes in advance of the full 1.0 release. The new  Upgrade guide  document provides detailed coverage of those breaking changes and how they affect plugin authors and Datasette API consumers. \n             \n                 \n                     The  /databasename?sql=  interface and JSON API for executing arbitrary SQL queries can now be found at  /databasename/-/query?sql= . Requests with a  ?sql=  parameter to the old endpoints will be redirected. Thanks,  Alex Garcia . ( #2360 ) \n                 \n                 \n                     Metadata about tables, databases, instances and columns is now stored in  Datasette's internal database . Thanks, Alex Garcia. ( #2341 ) \n                 \n                 \n                     Database write connections now execute using the  IMMEDIATE  isolation level for SQLite. This should help avoid a rare  SQLITE_BUSY  error that could occur when a transaction upgraded to a write mid-flight. ( #2358 ) \n                 \n                 \n                     Fix for a bug where canned queries with named parameters could fail against SQLite 3.46. ( #2353 ) \n                 \n                 \n                     Datasette now serves  E-Tag  headers for static files. Thanks,  Agustin Bacigalup . ( #2306 ) \n                 \n                 \n                     Dropdown menus now use a  z-index  that should avoid them being hidden by plugins. ( #2311 ) \n                 \n                 \n                     Incorrect table and row names are no longer reflected back on the resulting 404 page. ( #2359 ) \n                 \n                 \n                     Improved documentation for async usage of the  track_event(datasette, event)  hook. ( #2319 ) \n                 \n                 \n                     Fixed some HTTPX deprecation warnings. ( #2307 ) \n                 \n                 \n                     Datasette now serves a  <html lang=\"en\">  attribute. Thanks,  Charles Nepote . ( #2348 ) \n                 \n                 \n                     Datasette's automated tests now run against the maximum and minimum supported versions of SQLite: 3.25 (from September 2018) and 3.46 (from May 2024). Thanks, Alex Garcia. ( #2352 ) \n                 \n                 \n                     Fixed an issue where clicking twice on the URL output by  datasette --root  produced a confusing error. ( #2375 )", "sections_fts": 124, "rank": null}
{"rowid": 23, "title": "0.64.8 (2024-06-21)", "content": "Security improvement: 404 pages used to reflect content from the URL path, which could be used to display misleading information to Datasette users. 404 errors no longer display additional information from the URL. ( #2359 ) \n                 \n                 \n                     Backported a better fix for correctly extracting named parameters from canned query SQL against SQLite 3.46.0. ( #2353 )", "sections_fts": 124, "rank": null}
{"rowid": 24, "title": "0.64.7 (2024-06-12)", "content": "Fixed a bug where canned queries with named parameters threw an error when run against SQLite 3.46.0. ( #2353 )", "sections_fts": 124, "rank": null}
{"rowid": 25, "title": "1.0a13 (2024-03-12)", "content": "Each of the key concepts in Datasette now has an  actions menu , which plugins can use to add additional functionality targeting that entity. \n             \n                 \n                     Plugin hook:  view_actions()  for actions that can be applied to a SQL view. ( #2297 ) \n                 \n                 \n                     Plugin hook:  homepage_actions()  for actions that apply to the instance homepage. ( #2298 ) \n                 \n                 \n                     Plugin hook:  row_actions()  for actions that apply to the row page. ( #2299 ) \n                 \n                 \n                     Action menu items for all of the  *_actions()  plugin hooks can now return an optional  \"description\"  key, which will be displayed in the menu below the action label. ( #2294 ) \n                 \n                 \n                     Plugin hooks  documentation page is now organized with additional headings. ( #2300 ) \n                 \n                 \n                     Improved the display of action buttons on pages that also display metadata. ( #2286 ) \n                 \n                 \n                     The header and footer of the page now uses a subtle gradient effect, and options in the navigation menu are better visually defined. ( #2302 ) \n                 \n                 \n                     Table names that start with an underscore now default to hidden. ( #2104 ) \n                 \n                 \n                     pragma_table_list  has been added to the allow-list of SQLite pragma functions supported by Datasette.  select * from pragma_table_list()  is no longer blocked. ( #2104 )", "sections_fts": 124, "rank": null}
{"rowid": 26, "title": "1.0a12 (2024-02-29)", "content": "New  query_actions()  plugin hook, similar to  table_actions()  and  database_actions() . Can be used to add a menu of actions to the canned query or arbitrary SQL query page. ( #2283 ) \n                 \n                 \n                     New design for the button that opens the query, table and database actions menu. ( #2281 ) \n                 \n                 \n                     \"does not contain\" table filter for finding rows that do not contain a string. ( #2287 ) \n                 \n                 \n                     Fixed a bug in the  makeColumnActions(columnDetails)  JavaScript plugin mechanism where the column action menu was not fully reset in between each interaction. ( #2289 )", "sections_fts": 124, "rank": null}
{"rowid": 27, "title": "1.0a11 (2024-02-19)", "content": "The  \"replace\": true  argument to the  /db/table/-/insert  API now requires the actor to have the  update-row  permission. ( #2279 ) \n                 \n                 \n                     Fixed some UI bugs in the interactive permissions debugging tool. ( #2278 ) \n                 \n                 \n                     The column action menu now aligns better with the cog icon, and positions itself taking into account the width of the browser window. ( #2263 )", "sections_fts": 124, "rank": null}
{"rowid": 28, "title": "1.0a10 (2024-02-17)", "content": "The only changes in this alpha correspond to the way Datasette handles database transactions. ( #2277 ) \n             \n                 \n                     The  database.execute_write_fn()  method has a new  transaction=True  parameter. This defaults to  True  which means all functions executed using this method are now automatically wrapped in a transaction - previously the functions needed to roll transaction handling on their own, and many did not. \n                 \n                 \n                     Pass  transaction=False  to  execute_write_fn()  if you want to manually handle transactions in your function. \n                 \n                 \n                     Several internal Datasette features, including parts of the  JSON write API , had been failing to wrap their operations in a transaction. This has been fixed by the new  transaction=True  default.", "sections_fts": 124, "rank": null}
{"rowid": 29, "title": "1.0a9 (2024-02-16)", "content": "This alpha release adds basic alter table support to the Datasette Write API and fixes a permissions bug relating to the  /upsert  API endpoint.", "sections_fts": 124, "rank": null}
{"rowid": 30, "title": "Alter table support for create, insert, upsert and update", "content": "The  JSON write API  can now be used to apply simple alter table schema changes, provided the acting actor has the new  alter-table  permission. ( #2101 ) \n                 The only alter operation supported so far is adding new columns to an existing table. \n                 \n                     \n                         The  /db/-/create  API now adds new columns during large operations to create a table based on incoming example  \"rows\" , in the case where one of the later rows includes columns that were not present in the earlier batches. This requires the  create-table  but not the  alter-table  permission. \n                     \n                     \n                         When  /db/-/create  is called with rows in a situation where the table may have been already created, an  \"alter\": true  key can be included to indicate that any missing columns from the new rows should be added to the table. This requires the  alter-table  permission. \n                     \n                     \n                         /db/table/-/insert  and  /db/table/-/upsert  and  /db/table/row-pks/-/update  all now also accept  \"alter\": true , depending on the  alter-table  permission. \n                     \n                 \n                 Operations that alter a table now fire the new  alter-table event .", "sections_fts": 124, "rank": null}
{"rowid": 31, "title": "Permissions fix for the upsert API", "content": "The  /database/table/-/upsert API  had a minor permissions bug, only affecting Datasette instances that had configured the  insert-row  and  update-row  permissions to apply to a specific table rather than the database or instance as a whole. Full details in issue  #2262 . \n                 To avoid similar mistakes in the future the  datasette.permission_allowed()  method now specifies  default=  as a keyword-only argument.", "sections_fts": 124, "rank": null}
{"rowid": 32, "title": "Permission checks now consider opinions from every plugin", "content": "The  datasette.permission_allowed()  method previously consulted every plugin that implemented the  permission_allowed()  plugin hook and obeyed the opinion of the last plugin to return a value. ( #2275 ) \n                 Datasette now consults every plugin and checks to see if any of them returned  False  (the veto rule), and if none of them did, it then checks to see if any of them returned  True . \n                 This is explained at length in the new documentation covering  How permissions are resolved .", "sections_fts": 124, "rank": null}
{"rowid": 33, "title": "Other changes", "content": "The new  DATASETTE_TRACE_PLUGINS=1 environment variable  turns on detailed trace output for every executed plugin hook, useful for debugging and understanding how the plugin system works at a low level. ( #2274 ) \n                     \n                     \n                         Datasette on Python 3.9 or above marks its non-cryptographic uses of the MD5 hash function as  usedforsecurity=False , for compatibility with FIPS systems. ( #2270 ) \n                     \n                     \n                         SQL relating to  Datasette's internal database  now executes inside a transaction, avoiding a potential database locked error. ( #2273 ) \n                     \n                     \n                         The  /-/threads  debug page now identifies the database in the name associated with each dedicated write thread. ( #2265 ) \n                     \n                     \n                         The  /db/-/create  API now fires a  insert-rows  event if rows were inserted after the table was created. ( #2260 )", "sections_fts": 124, "rank": null}
{"rowid": 34, "title": "1.0a8 (2024-02-07)", "content": "This alpha release continues the migration of Datasette's configuration from  metadata.yaml  to the new  datasette.yaml  configuration file, introduces a new system for JavaScript plugins and adds several new plugin hooks. \n             See  Datasette 1.0a8: JavaScript plugins, new plugin hooks and plugin configuration in datasette.yaml  for an annotated version of these release notes.", "sections_fts": 124, "rank": null}
{"rowid": 35, "title": "Configuration", "content": "Plugin configuration now lives in the  datasette.yaml configuration file , passed to Datasette using the  -c/--config  option. Thanks, Alex Garcia. ( #2093 ) \n                         datasette -c datasette.yaml \n                         Where  datasette.yaml  contains configuration that looks like this: \n                         plugins:\n  datasette-cluster-map:\n    latitude_column: xlat\n    longitude_column: xlon \n                         Previously plugins were configured in  metadata.yaml , which was confusing as plugin settings were unrelated to database and table metadata. \n                     \n                     \n                         The  -s/--setting  option can now be used to set plugin configuration as well. See  Configuration via the command-line  for details. ( #2252 ) \n                         The above YAML configuration example using  -s/--setting  looks like this: \n                         datasette mydatabase.db \\\n  -s plugins.datasette-cluster-map.latitude_column xlat \\\n  -s plugins.datasette-cluster-map.longitude_column xlon \n                     \n                     \n                         The new  /-/config  page shows the current instance configuration, after redacting keys that could contain sensitive data such as API keys or passwords. ( #2254 ) \n                     \n                     \n                         Existing Datasette installations may already have configuration set in  metadata.yaml  that should be migrated to  datasette.yaml . To avoid breaking these installations, Datasette will silently treat table configuration, plugin configuration and allow blocks in metadata as if they had been specified in configuration instead. ( #2247 ) ( #2248 ) ( #2249 ) \n                     \n                 \n                 Note that the  datasette publish  command has not yet been updated to accept a  datasette.yaml  configuration file. This will be addressed in  #2195  but for the moment you can include those settings in  metadata.yaml  instead.", "sections_fts": 124, "rank": null}
{"rowid": 36, "title": "JavaScript plugins", "content": "Datasette now includes a  JavaScript plugins mechanism , allowing JavaScript to customize Datasette in a way that can collaborate with other plugins. \n                 This provides two initial hooks, with more to come in the future: \n                 \n                     \n                         makeAboveTablePanelConfigs()  can add additional panels to the top of the table page. \n                     \n                     \n                         makeColumnActions()  can add additional actions to the column menu. \n                     \n                 \n                 Thanks  Cameron Yick  for contributing this feature. ( #2052 )", "sections_fts": 124, "rank": null}
{"rowid": 37, "title": "Plugin hooks", "content": "New  jinja2_environment_from_request(datasette, request, env)  plugin hook, which can be used to customize the current Jinja environment based on the incoming request. This can be used to modify the template lookup path based on the incoming request hostname, among other things. ( #2225 ) \n                     \n                     \n                         New  family of template slot plugin hooks :  top_homepage ,  top_database ,  top_table ,  top_row ,  top_query ,  top_canned_query . Plugins can use these to provide additional HTML to be injected at the top of the corresponding pages. ( #1191 ) \n                     \n                     \n                         \n                             \n                                 New  track_event() mechanism  for plugins to emit and receive events when certain events occur within Datasette. ( #2240 ) \n                                 \n                                     \n                                         \n                                             Plugins can register additional event classes using  register_events(datasette) . \n                                         \n                                         \n                                             They can then trigger those events with the  datasette.track_event(event)  internal method. \n                                         \n                                         \n                                             Plugins can subscribe to notifications of events using the  track_event(datasette, event)  plugin hook. \n                                         \n                                         \n                                             Datasette core now emits  login ,  logout ,  create-token ,  create-table ,  drop-table ,  insert-rows ,  upsert-rows ,  update-row ,  delete-row  events,  documented here . \n                                         \n                                     \n                                 \n                             \n                         \n                     \n                     \n                         New internal function for plugin authors:  await db.execute_isolated_fn(fn) , for creating a new SQLite connection, executing code and then closing that connection, all while preventing other code from writing to that particular database. This connection will not have the  prepare_connection()  plugin hook executed against it, allowing plugins to perform actions that might otherwise be blocked by existing connection configuration. ( #2218 )", "sections_fts": 124, "rank": null}
{"rowid": 38, "title": "Documentation", "content": "Documentation describing  how to write tests that use signed actor cookies  using  datasette.client.actor_cookie() . ( #1830 ) \n                     \n                     \n                         Documentation on how to  register a plugin for the duration of a test . ( #2234 ) \n                     \n                     \n                         The  configuration documentation  now shows examples of both YAML and JSON for each setting.", "sections_fts": 124, "rank": null}
{"rowid": 39, "title": "Minor fixes", "content": "Datasette no longer attempts to run SQL queries in parallel when rendering a table page, as this was leading to some rare crashing bugs. ( #2189 ) \n                     \n                     \n                         Fixed warning:  DeprecationWarning: pkg_resources is deprecated as an API  ( #2057 ) \n                     \n                     \n                         Fixed bug where  ?_extra=columns  parameter returned an incorrectly shaped response. ( #2230 )", "sections_fts": 124, "rank": null}
{"rowid": 40, "title": "0.64.6 (2023-12-22)", "content": "Fixed a bug where CSV export with expanded labels could fail if a foreign key reference did not correctly resolve. ( #2214 )", "sections_fts": 124, "rank": null}
{"rowid": 41, "title": "0.64.5 (2023-10-08)", "content": "Dropped dependency on  click-default-group-wheel , which could cause a dependency conflict. ( #2197 )", "sections_fts": 124, "rank": null}
{"rowid": 42, "title": "1.0a7 (2023-09-21)", "content": "Fix for a crashing bug caused by viewing the table page for a named in-memory database. ( #2189 )", "sections_fts": 124, "rank": null}
{"rowid": 43, "title": "0.64.4 (2023-09-21)", "content": "Fix for a crashing bug caused by viewing the table page for a named in-memory database. ( #2189 )", "sections_fts": 124, "rank": null}
{"rowid": 44, "title": "1.0a6 (2023-09-07)", "content": "New plugin hook:  actors_from_ids(datasette, actor_ids)  and an internal method to accompany it,  await .actors_from_ids(actor_ids) . This mechanism is intended to be used by plugins that may need to display the actor who was responsible for something managed by that plugin: they can now resolve the recorded IDs of actors into the full actor objects. ( #2181 ) \n                 \n                 \n                     DATASETTE_LOAD_PLUGINS  environment variable for  controlling which plugins  are loaded by Datasette. ( #2164 ) \n                 \n                 \n                     Datasette now checks if the user has permission to view a table linked to by a foreign key before turning that foreign key into a clickable link. ( #2178 ) \n                 \n                 \n                     The  execute-sql  permission now implies that the actor can also view the database and instance. ( #2169 ) \n                 \n                 \n                     Documentation describing a pattern for building plugins that themselves  define further hooks  for other plugins. ( #1765 ) \n                 \n                 \n                     Datasette is now tested against the Python 3.12 preview. ( #2175 )", "sections_fts": 124, "rank": null}
{"rowid": 45, "title": "1.0a5 (2023-08-29)", "content": "When restrictions are applied to  API tokens , those restrictions now behave slightly differently: applying the  view-table  restriction will imply the ability to  view-database  for the database containing that table, and both  view-table  and  view-database  will imply  view-instance . Previously you needed to create a token with restrictions that explicitly listed  view-instance  and  view-database  and  view-table  in order to view a table without getting a permission denied error. ( #2102 ) \n                 \n                 \n                     New  datasette.yaml  (or  .json ) configuration file, which can be specified using  datasette -c path-to-file . The goal here to consolidate settings, plugin configuration, permissions, canned queries, and other Datasette configuration into a single single file, separate from  metadata.yaml . The legacy  settings.json  config file used for  Configuration directory mode  has been removed, and  datasette.yaml  has a  \"settings\"  section where the same settings key/value pairs can be included. In the next future alpha release, more configuration such as plugins/permissions/canned queries will be moved to the  datasette.yaml  file. See  #2093  for more details. Thanks, Alex Garcia. \n                 \n                 \n                     The  -s/--setting  option can now take dotted paths to nested settings. These will then be used to set or over-ride the same options as are present in the new configuration file. ( #2156 ) \n                 \n                 \n                     New  --actor '{\"id\": \"json-goes-here\"}'  option for use with  datasette --get  to treat the simulated request as being made by a specific actor, see  datasette --get . ( #2153 ) \n                 \n                 \n                     The Datasette  _internal  database has had some changes. It no longer shows up in the  datasette.databases  list by default, and is now instead available to plugins using the  datasette.get_internal_database() . Plugins are invited to use this as a private database to store configuration and settings and secrets that should not be made visible through the default Datasette interface. Users can pass the new   --internal internal.db  option to persist that internal database to disk. Thanks, Alex Garcia. ( #2157 ).", "sections_fts": 124, "rank": null}
{"rowid": 46, "title": "1.0a4 (2023-08-21)", "content": "This alpha fixes a security issue with the  /-/api  API explorer. On authenticated Datasette instances (instances protected using plugins such as  datasette-auth-passwords ) the API explorer interface could reveal the names of databases and tables within the protected instance. The data stored in those tables was not revealed. \n             For more information and workarounds, read  the security advisory . The issue has been present in every previous alpha version of Datasette 1.0: versions 1.0a0, 1.0a1, 1.0a2 and 1.0a3. \n             Also in this alpha: \n             \n                 \n                     The new  datasette plugins --requirements  option outputs a list of currently installed plugins in Python  requirements.txt  format, useful for duplicating that installation elsewhere. ( #2133 ) \n                 \n                 \n                     Writable canned queries  can now define a  on_success_message_sql  field in their configuration, containing a SQL query that should be executed upon successful completion of the write operation in order to generate a message to be shown to the user. ( #2138 ) \n                 \n                 \n                     The automatically generated border color for a database is now shown in more places around the application. ( #2119 ) \n                 \n                 \n                     Every instance of example shell script code in the documentation should now include a working copy button, free from additional syntax. ( #2140 )", "sections_fts": 124, "rank": null}
{"rowid": 47, "title": "1.0a3 (2023-08-09)", "content": "This alpha release previews the updated design for Datasette's default JSON API. ( #782 ) \n             The new  default JSON representation  for both table pages ( /dbname/table.json ) and arbitrary SQL queries ( /dbname.json?sql=... ) is now shaped like this: \n             {\n  \"ok\": true,\n  \"rows\": [\n    {\n      \"id\": 3,\n      \"name\": \"Detroit\"\n    },\n    {\n      \"id\": 2,\n      \"name\": \"Los Angeles\"\n    },\n    {\n      \"id\": 4,\n      \"name\": \"Memnonia\"\n    },\n    {\n      \"id\": 1,\n      \"name\": \"San Francisco\"\n    }\n  ],\n  \"truncated\": false\n} \n             Tables will include an additional  \"next\"  key for pagination, which can be passed to  ?_next=  to fetch the next page of results. \n             The various  ?_shape=  options continue to work as before - see  Different shapes  for details. \n             A new  ?_extra=  mechanism is available for tables, but has not yet been stabilized or documented. Details on that are available in  #262 .", "sections_fts": 124, "rank": null}
{"rowid": 48, "title": "Smaller changes", "content": "Datasette documentation now shows YAML examples for  Metadata  by default, with a tab interface for switching to JSON. ( #1153 ) \n                     \n                     \n                         register_output_renderer(datasette)  plugins now have access to  error  and  truncated  arguments, allowing them to display error messages and take into account truncated results. ( #2130 ) \n                     \n                     \n                         render_cell()  plugin hook now also supports an optional  request  argument. ( #2007 ) \n                     \n                     \n                         New  Justfile  to support development workflows for Datasette using  Just . \n                     \n                     \n                         datasette.render_template()  can now accepts a  datasette.views.Context  subclass as an alternative to a dictionary. ( #2127 ) \n                     \n                     \n                         datasette install -e path  option for editable installations, useful while developing plugins. ( #2106 ) \n                     \n                     \n                         When started with the  --cors  option Datasette now serves an  Access-Control-Max-Age: 3600  header, ensuring CORS OPTIONS requests are repeated no more than once an hour. ( #2079 ) \n                     \n                     \n                         Fixed a bug where the  _internal  database could display  None  instead of  null  for in-memory databases. ( #1970 )", "sections_fts": 124, "rank": null}
{"rowid": 49, "title": "0.64.2 (2023-03-08)", "content": "Fixed a bug with  datasette publish cloudrun  where deploys all used the same Docker image tag. This was mostly inconsequential as the service is deployed as soon as the image has been pushed to the registry, but could result in the incorrect image being deployed if two different deploys for two separate services ran at exactly the same time. ( #2036 )", "sections_fts": 124, "rank": null}
{"rowid": 50, "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 )", "sections_fts": 124, "rank": null}
{"rowid": 51, "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 )", "sections_fts": 124, "rank": null}
{"rowid": 52, "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 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 )", "sections_fts": 124, "rank": null}
{"rowid": 53, "title": "1.0a2 (2022-12-14)", "content": "The third Datasette 1.0 alpha release adds upsert support to the JSON API, plus the ability to specify finely grained permissions when creating an API token. \n             See  Datasette 1.0a2: Upserts and finely grained permissions  for an extended, annotated version of these release notes. \n             \n                 \n                     New  /db/table/-/upsert  API,  documented here . upsert is an update-or-insert: existing rows will have specified keys updated, but if no row matches the incoming primary key a brand new row will be inserted instead. ( #1878 ) \n                 \n                 \n                     New  register_permissions(datasette)  plugin hook. Plugins can now register named permissions, which will then be listed in various interfaces that show available permissions. ( #1940 ) \n                 \n                 \n                     The  /db/-/create  API for  creating a table  now accepts  \"ignore\": true  and  \"replace\": true  options when called with the  \"rows\"  property that creates a new table based on an example set of rows. This means the API can be called multiple times with different rows, setting rules for what should happen if a primary key collides with an existing row. ( #1927 ) \n                 \n                 \n                     Arbitrary permissions can now be configured at the instance, database and resource (table, SQL view or canned query) level in Datasette's  Metadata  JSON and YAML files. The new  \"permissions\"  key can be used to specify which actors should have which permissions. See  Other permissions in datasette.yaml  for details. ( #1636 ) \n                 \n                 \n                     The  /-/create-token  page can now be used to create API tokens which are restricted to just a subset of actions, including against specific databases or resources. See  API Tokens  for details. ( #1947 ) \n                 \n                 \n                     Likewise, the  datasette create-token  CLI command can now create tokens with  a subset of permissions . ( #1855 ) \n                 \n                 \n                     New  datasette.create_token() API method  for programmatically creating signed API tokens. ( #1951 ) \n                 \n                 \n                     /db/-/create  API now requires actor to have  insert-row  permission in order to use the  \"row\"  or  \"rows\"  properties. ( #1937 )", "sections_fts": 124, "rank": null}
{"rowid": 54, "title": "1.0a1 (2022-12-01)", "content": "Write APIs now serve correct CORS headers if Datasette is started in  --cors  mode. See the full list of  CORS headers  in the documentation. ( #1922 ) \n                 \n                 \n                     Fixed a bug where the  _memory  database could be written to even though writes were not persisted. ( #1917 ) \n                 \n                 \n                     The  https://latest.datasette.io/  demo instance now includes an  ephemeral  database which can be used to test Datasette's write APIs, using the new  datasette-ephemeral-tables  plugin to drop any created tables after five minutes. This database is only available if you sign in as the root user using the link on the homepage. ( #1915 ) \n                 \n                 \n                     Fixed a bug where hitting the write endpoints with a  GET  request returned a 500 error. It now returns a 405 (method not allowed) error instead. ( #1916 ) \n                 \n                 \n                     The list of endpoints in the API explorer now lists mutable databases first. ( #1918 ) \n                 \n                 \n                     The  \"ignore\": true  and  \"replace\": true  options for the insert API are  now documented . ( #1924 )", "sections_fts": 124, "rank": null}
{"rowid": 55, "title": "1.0a0 (2022-11-29)", "content": "This first alpha release of Datasette 1.0 introduces a brand new collection of APIs for writing to the database ( #1850 ), as well as a new API token mechanism baked into Datasette core. Previously, API tokens have only been supported by installing additional plugins. \n             This is very much a preview: expect many more backwards incompatible API changes prior to the full 1.0 release. \n             Feedback enthusiastically welcomed, either through  issue comments  or via the  Datasette Discord  community.", "sections_fts": 124, "rank": null}
{"rowid": 56, "title": "Signed API tokens", "content": "New  /-/create-token  page allowing authenticated users to create signed API tokens that can act on their behalf, see  API Tokens . ( #1852 ) \n                     \n                     \n                         New  datasette create-token  command for creating tokens from the command line:  datasette create-token . \n                     \n                     \n                         New  allow_signed_tokens  setting which can be used to turn off signed token support. ( #1856 ) \n                     \n                     \n                         New  max_signed_tokens_ttl  setting for restricting the maximum allowed duration of a signed token. ( #1858 )", "sections_fts": 124, "rank": null}
{"rowid": 57, "title": "Write API", "content": "New API explorer at  /-/api  for trying out the API. ( #1871 ) \n                     \n                     \n                         /db/-/create  API for  Creating a table . ( #1882 ) \n                     \n                     \n                         /db/table/-/insert  API for  Inserting rows . ( #1851 ) \n                     \n                     \n                         /db/table/-/drop  API for  Dropping tables . ( #1874 ) \n                     \n                     \n                         /db/table/pk/-/update  API for  Updating a row . ( #1863 ) \n                     \n                     \n                         /db/table/pk/-/delete  API for  Deleting a row . ( #1864 )", "sections_fts": 124, "rank": null}
{"rowid": 58, "title": "0.63.2 (2022-11-18)", "content": "Fixed a bug in  datasette publish heroku  where deployments failed due to an older version of Python being requested. ( #1905 ) \n                 \n                 \n                     New  datasette publish heroku --generate-dir <dir>  option for generating a Heroku deployment directory without deploying it.", "sections_fts": 124, "rank": null}
{"rowid": 59, "title": "0.63.1 (2022-11-10)", "content": "Fixed a bug where Datasette's table filter form would not redirect correctly when run behind a proxy using the  base_url  setting. ( #1883 ) \n                 \n                 \n                     SQL query is now shown wrapped in a  <textarea>  if a query exceeds a time limit. ( #1876 ) \n                 \n                 \n                     Fixed an intermittent \"Too many open files\" error while running the test suite. ( #1843 ) \n                 \n                 \n                     New  db.close()  internal method.", "sections_fts": 124, "rank": null}
{"rowid": 60, "title": "0.63 (2022-10-27)", "content": "See  Datasette 0.63: The annotated release notes  for more background on the changes in this release.", "sections_fts": 124, "rank": null}
{"rowid": 61, "title": "Features", "content": "Now tested against Python 3.11. Docker containers used by  datasette publish  and  datasette package  both now use that version of Python. ( #1853 ) \n                     \n                     \n                         --load-extension  option now supports entrypoints. Thanks, Alex Garcia. ( #1789 ) \n                     \n                     \n                         Facet size can now be set per-table with the new  facet_size  table metadata option. ( #1804 ) \n                     \n                     \n                         The  truncate_cells_html  setting now also affects long URLs in columns. ( #1805 ) \n                     \n                     \n                         The non-JavaScript SQL editor textarea now increases height to fit the SQL query. ( #1786 ) \n                     \n                     \n                         Facets are now displayed with better line-breaks in long values. Thanks, Daniel Rech. ( #1794 ) \n                     \n                     \n                         The  settings.json  file used in  Configuration directory mode  is now validated on startup. ( #1816 ) \n                     \n                     \n                         SQL queries can now include leading SQL comments, using  /* ... */  or  -- ...  syntax. Thanks,  Charles Nepote. ( #1860 ) \n                     \n                     \n                         SQL query is now re-displayed when terminated with a time limit error. ( #1819 ) \n                     \n                     \n                         The  inspect data  mechanism is now used to speed up server startup - thanks, Forest Gregg. ( #1834 ) \n                     \n                     \n                         In  Configuration directory mode  databases with filenames ending in  .sqlite  or  .sqlite3  are now automatically added to the Datasette instance. ( #1646 ) \n                     \n                     \n                         Breadcrumb navigation display now respects the current user's permissions. ( #1831 )", "sections_fts": 124, "rank": null}
{"rowid": 62, "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 )", "sections_fts": 124, "rank": null}
{"rowid": 63, "title": "Documentation", "content": "New tutorial:  Cleaning data with sqlite-utils and Datasette . \n                     \n                     \n                         Screenshots in the documentation are now maintained using  shot-scraper , as described in  Automating screenshots for the Datasette documentation using shot-scraper . ( #1844 ) \n                     \n                     \n                         More detailed command descriptions on the  CLI reference  page. ( #1787 ) \n                     \n                     \n                         New documentation on  Running Datasette using OpenRC  - thanks, Adam Simpson. ( #1825 )", "sections_fts": 124, "rank": null}
{"rowid": 64, "title": "0.62 (2022-08-14)", "content": "Datasette can now run entirely in your browser using WebAssembly. Try out  Datasette Lite , take a look  at the code  or read more about it in  Datasette Lite: a server-side Python web application running in a browser . \n             Datasette now has a  Discord community  for questions and discussions about Datasette and its ecosystem of projects.", "sections_fts": 124, "rank": null}
{"rowid": 65, "title": "Features", "content": "Datasette is now compatible with  Pyodide .  This is the enabling technology behind  Datasette Lite . ( #1733 ) \n                     \n                     \n                         Database file downloads now implement conditional GET using ETags. ( #1739 ) \n                     \n                     \n                         HTML for facet results and suggested results has been extracted out into new templates  _facet_results.html  and  _suggested_facets.html . Thanks, M. Nasimul Haque. ( #1759 ) \n                     \n                     \n                         Datasette now runs some SQL queries in parallel. This has limited impact on performance, see  this research issue  for details. \n                     \n                     \n                         New  --nolock  option for ignoring file locks when opening read-only databases. ( #1744 ) \n                     \n                     \n                         Spaces in the database names in URLs are now encoded as  +  rather than  ~20 . ( #1701 ) \n                     \n                     \n                         <Binary: 2427344 bytes>  is now displayed as  <Binary: 2,427,344 bytes>  and is accompanied by tooltip showing \"2.3MB\". ( #1712 ) \n                     \n                     \n                         The base Docker image used by  datasette publish cloudrun ,  datasette package  and the  official Datasette image  has been upgraded to  3.10.6-slim-bullseye .  ( #1768 ) \n                     \n                     \n                         Canned writable queries against immutable databases now show a warning message. ( #1728 ) \n                     \n                     \n                         datasette publish cloudrun  has a new  --timeout  option which can be used to increase the time limit applied by the Google Cloud build environment. Thanks, Tim Sherratt. ( #1717 ) \n                     \n                     \n                         datasette publish cloudrun  has new  --min-instances  and  --max-instances  options. ( #1779 )", "sections_fts": 124, "rank": null}
{"rowid": 66, "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 )", "sections_fts": 124, "rank": null}
{"rowid": 67, "title": "Bug fixes", "content": "Don't show the facet option in the cog menu if faceting is not allowed. ( #1683 ) \n                     \n                     \n                         ?_sort  and  ?_sort_desc  now work if the column that is being sorted has been excluded from the query using  ?_col=  or  ?_nocol= . ( #1773 ) \n                     \n                     \n                         Fixed bug where  ?_sort_desc  was duplicated in the URL every time the Apply button was clicked. ( #1738 )", "sections_fts": 124, "rank": null}
{"rowid": 68, "title": "Documentation", "content": "Examples in the documentation now include a copy-to-clipboard button. ( #1748 ) \n                     \n                     \n                         Documentation now uses the  Furo  Sphinx theme. ( #1746 ) \n                     \n                     \n                         Code examples in the documentation are now all formatted using Black. ( #1718 ) \n                     \n                     \n                         Request.fake()  method is now documented, see  Request object . \n                     \n                     \n                         New documentation for plugin authors:  Registering a plugin for the duration of a test . ( #903 )", "sections_fts": 124, "rank": null}
{"rowid": 69, "title": "0.61.1 (2022-03-23)", "content": "Fixed a bug where databases with a different route from their name (as used by the  datasette-hashed-urls plugin ) returned errors when executing custom SQL queries. ( #1682 )", "sections_fts": 124, "rank": null}
{"rowid": 70, "title": "0.61 (2022-03-23)", "content": "In preparation for Datasette 1.0, this release includes two potentially backwards-incompatible changes. Hashed URL mode has been moved to a separate plugin, and the way Datasette generates URLs to databases and tables with special characters in their name such as  /  and  .  has changed. \n             Datasette also now requires Python 3.7 or higher. \n             \n                 \n                     URLs within Datasette now use a different encoding scheme for tables or databases that include \"special\" characters outside of the range of  a-zA-Z0-9_- . This scheme is explained here:  Tilde encoding . ( #1657 ) \n                 \n                 \n                     Removed hashed URL mode from Datasette. The new  datasette-hashed-urls  plugin can be used to achieve the same result, see  datasette-hashed-urls  for details. ( #1661 ) \n                 \n                 \n                     Databases can now have a custom path within the Datasette instance that is independent of the database name, using the  db.route  property. ( #1668 ) \n                 \n                 \n                     Datasette is now covered by a  Code of Conduct . ( #1654 ) \n                 \n                 \n                     Python 3.6 is no longer supported. ( #1577 ) \n                 \n                 \n                     Tests now run against Python 3.11-dev. ( #1621 ) \n                 \n                 \n                     New  datasette.ensure_permissions(actor, permissions)  internal method for checking multiple permissions at once. ( #1675 ) \n                 \n                 \n                     New  datasette.check_visibility(actor, action, resource=None)  internal method for checking if a user can see a resource that would otherwise be invisible to unauthenticated users. ( #1678 ) \n                 \n                 \n                     Table and row HTML pages now include a  <link rel=\"alternate\" type=\"application/json+datasette\" href=\"...\">  element and return a  Link: URL; rel=\"alternate\"; type=\"application/json+datasette\"  HTTP header pointing to the JSON version of those pages. ( #1533 ) \n                 \n                 \n                     Access-Control-Expose-Headers: Link  is now added to the CORS headers, allowing remote JavaScript to access that header. \n                 \n                 \n                     Canned queries are now shown at the top of the database page, directly below the SQL editor. Previously they were shown at the bottom, below the list of tables. ( #1612 ) \n                 \n                 \n                     Datasette now has a default favicon. ( #1603 ) \n                 \n                 \n                     sqlite_stat  tables are now hidden by default. ( #1587 ) \n                 \n                 \n                     SpatiaLite tables  data_licenses ,  KNN  and  KNN2  are now hidden by default. ( #1601 ) \n                 \n                 \n                     SQL query tracing mechanism now works for queries executed in  asyncio  sub-tasks, such as those created by  asyncio.gather() . ( #1576 ) \n                 \n                 \n                     datasette.tracer  mechanism is now documented. \n                 \n                 \n                     Common Datasette symbols can now be imported directly from the top-level  datasette  package, see  Import shortcuts . Those symbols are  Response ,  Forbidden ,  NotFound ,  hookimpl ,  actor_matches_allow . ( #957 ) \n                 \n                 \n                     /-/versions  page now returns additional details for libraries used by SpatiaLite. ( #1607 ) \n                 \n                 \n                     Documentation now links to the  Datasette Tutorials . \n                 \n                 \n                     Datasette will now also look for SpatiaLite in  /opt/homebrew  - thanks, Dan Peterson. ( #1649 ) \n                 \n                 \n                     Fixed bug where  custom pages  did not work on Windows. Thanks, Robert Christie. ( #1545 ) \n                 \n                 \n                     Fixed error caused when a table had a column named  n . ( #1228 )", "sections_fts": 124, "rank": null}
{"rowid": 71, "title": "0.60.2 (2022-02-07)", "content": "Fixed a bug where Datasette would open the same file twice with two different database names if you ran  datasette file.db file.db . ( #1632 )", "sections_fts": 124, "rank": null}
{"rowid": 72, "title": "0.60.1 (2022-01-20)", "content": "Fixed a bug where installation on Python 3.6 stopped working due to a change to an underlying dependency. This release can now be installed on Python 3.6, but is the last release of Datasette that will support anything less than Python 3.7. ( #1609 )", "sections_fts": 124, "rank": null}
{"rowid": 73, "title": "0.60 (2022-01-13)", "content": "", "sections_fts": 124, "rank": null}
{"rowid": 74, "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 )", "sections_fts": 124, "rank": null}
{"rowid": 75, "title": "Faceting", "content": "The number of unique values in a facet is now always displayed. Previously it was only displayed if the user specified  ?_facet_size=max . ( #1556 ) \n                     \n                     \n                         Facets of type  date  or  array  can now be configured in  metadata.json , see  Facets in metadata . Thanks, David Larlet. ( #1552 ) \n                     \n                     \n                         New  ?_nosuggest=1  parameter for table views, which disables facet suggestion. ( #1557 ) \n                     \n                     \n                         Fixed bug where  ?_facet_array=tags&_facet=tags  would only display one of the two selected facets. ( #625 )", "sections_fts": 124, "rank": null}
{"rowid": 76, "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 )", "sections_fts": 124, "rank": null}
{"rowid": 77, "title": "0.59.4 (2021-11-29)", "content": "Fixed bug where columns with a leading underscore could not be removed from the interactive filters list. ( #1527 ) \n                 \n                 \n                     Fixed bug where columns with a leading underscore were not correctly linked to by the \"Links from other tables\" interface on the row page. ( #1525 ) \n                 \n                 \n                     Upgraded dependencies  aiofiles ,  black  and  janus .", "sections_fts": 124, "rank": null}
{"rowid": 78, "title": "0.59.3 (2021-11-20)", "content": "Fixed numerous bugs when running Datasette  behind a proxy  with a prefix URL path using the  base_url  setting. A live demo of this mode is now available at  datasette-apache-proxy-demo.datasette.io/prefix/ . ( #1519 ,  #838 ) \n                 \n                 \n                     ?column__arraycontains=  and  ?column__arraynotcontains=  table parameters now also work against SQL views. ( #448 ) \n                 \n                 \n                     ?_facet_array=column  no longer returns incorrect counts if columns contain the same value more than once.", "sections_fts": 124, "rank": null}
{"rowid": 79, "title": "0.59.2 (2021-11-13)", "content": "Column names with a leading underscore now work correctly when used as a facet. ( #1506 ) \n                 \n                 \n                     Applying  ?_nocol=  to a column no longer removes that column from the filtering interface. ( #1503 ) \n                 \n                 \n                     Official Datasette Docker container now uses Debian Bullseye as the base image. ( #1497 ) \n                 \n                 \n                     Datasette is four years old today! Here's the  original release announcement  from 2017.", "sections_fts": 124, "rank": null}
{"rowid": 80, "title": "0.59.1 (2021-10-24)", "content": "Fix compatibility with Python 3.10. ( #1482 ) \n                 \n                 \n                     Documentation on how to use  Named parameters  with integer and floating point values. ( #1496 )", "sections_fts": 124, "rank": null}
{"rowid": 81, "title": "0.59 (2021-10-14)", "content": "Columns can now have associated metadata descriptions in  metadata.json , see  Column descriptions . ( #942 ) \n                 \n                 \n                     New  register_commands()  plugin hook allows plugins to register additional Datasette CLI commands, e.g.  datasette mycommand file.db . ( #1449 ) \n                 \n                 \n                     Adding  ?_facet_size=max  to a table page now shows the number of unique values in each facet. ( #1423 ) \n                 \n                 \n                     Upgraded dependency  httpx 0.20  - the undocumented  allow_redirects=  parameter to  datasette.client  is now  follow_redirects= , and defaults to  False  where it previously defaulted to  True . ( #1488 ) \n                 \n                 \n                     The  --cors  option now causes Datasette to return the  Access-Control-Allow-Headers: Authorization  header, in addition to  Access-Control-Allow-Origin: * . ( #1467 ) \n                 \n                 \n                     Code that figures out which named parameters a SQL query takes in order to display form fields for them is no longer confused by strings that contain colon characters. ( #1421 ) \n                 \n                 \n                     Renamed  --help-config  option to  --help-settings . ( #1431 ) \n                 \n                 \n                     datasette.databases  property is now a documented API. ( #1443 ) \n                 \n                 \n                     The  base.html  template now wraps everything other than the  <footer>  in a  <div class=\"not-footer\">  element, to help with advanced CSS customization. ( #1446 ) \n                 \n                 \n                     The  render_cell()  plugin hook can now return an awaitable function. This means the hook can execute SQL queries. ( #1425 ) \n                 \n                 \n                     register_routes(datasette)  plugin hook now accepts an optional  datasette  argument. ( #1404 ) \n                 \n                 \n                     New  hide_sql  canned query option for defaulting to hiding the SQL query used by a canned query, see  Additional canned query options . ( #1422 ) \n                 \n                 \n                     New  --cpu  option for  datasette publish cloudrun . ( #1420 ) \n                 \n                 \n                     If  Rich  is installed in the same virtual environment as Datasette, it will be used to provide enhanced display of error tracebacks on the console. ( #1416 ) \n                 \n                 \n                     datasette.utils   parse_metadata(content)  function, used by the new  datasette-remote-metadata plugin , is now a documented API. ( #1405 ) \n                 \n                 \n                     Fixed bug where  ?_next=x&_sort=rowid  could throw an error. ( #1470 ) \n                 \n                 \n                     Column cog menu no longer shows the option to facet by a column that is already selected by the default facets in metadata. ( #1469 )", "sections_fts": 124, "rank": null}
{"rowid": 82, "title": "0.58.1 (2021-07-16)", "content": "Fix for an intermittent race condition caused by the  refresh_schemas()  internal function. ( #1231 )", "sections_fts": 124, "rank": null}
{"rowid": 83, "title": "0.58 (2021-07-14)", "content": "New  datasette --uds /tmp/datasette.sock  option for binding Datasette to a Unix domain socket, see  proxy documentation  ( #1388 ) \n                 \n                 \n                     \"searchmode\": \"raw\"  table metadata option for defaulting a table to executing SQLite full-text search syntax without first escaping it, see  Advanced SQLite search queries . ( #1389 ) \n                 \n                 \n                     New plugin hook:  get_metadata() , for returning custom metadata for an instance, database or table. Thanks, Brandon Roberts! ( #1384 ) \n                 \n                 \n                     New plugin hook:  skip_csrf(datasette, scope) , for opting out of CSRF protection based on the incoming request. ( #1377 ) \n                 \n                 \n                     The  menu_links() ,  table_actions()  and  database_actions()  plugin hooks all gained a new optional  request  argument providing access to the current request. ( #1371 ) \n                 \n                 \n                     Major performance improvement for Datasette faceting. ( #1394 ) \n                 \n                 \n                     Improved documentation for  Running Datasette behind a proxy  to recommend using  ProxyPreservehost On  with Apache. ( #1387 ) \n                 \n                 \n                     POST  requests to endpoints that do not support that HTTP verb now return a 405 error. \n                 \n                 \n                     db.path  can now be provided as a  pathlib.Path  object, useful when writing unit tests for plugins. Thanks, Chris Amico. ( #1365 )", "sections_fts": 124, "rank": null}
{"rowid": 84, "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": 124, "rank": null}
{"rowid": 85, "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": 124, "rank": null}
{"rowid": 86, "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": 124, "rank": null}
{"rowid": 87, "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": 124, "rank": null}
{"rowid": 88, "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": 124, "rank": null}
{"rowid": 89, "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": 124, "rank": null}
{"rowid": 90, "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": 124, "rank": null}
{"rowid": 91, "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": 124, "rank": null}
{"rowid": 92, "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": 124, "rank": null}
{"rowid": 93, "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": 124, "rank": null}
{"rowid": 94, "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": 124, "rank": null}
{"rowid": 95, "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": 124, "rank": null}
{"rowid": 96, "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": 124, "rank": null}
{"rowid": 97, "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": 124, "rank": null}
{"rowid": 98, "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": 124, "rank": null}
{"rowid": 99, "title": "0.52.5 (2020-12-09)", "content": "Fix for error caused by combining the  _searchmode=raw  and  ?_search_COLUMN  parameters. ( #1134 )", "sections_fts": 124, "rank": null}
{"rowid": 100, "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": 124, "rank": null}