Datasette 1.0a14 includes some breaking changes to how metadata works for plugins, described in detail in the new upgrade guide. See also the annotated release notes that accompany this release.

Datasette 1.0a10 is a focused alpha that changes some internal details about how Datasette handles transactions. The datasette.execute_write_fn() internal method now wraps the function in a database transaction unless you pass transaction=False.

Datasette 1.0a9 adds basic alter table support to the JSON API, tweaks how permissions works and introduces some new plugin debugging utilities.

Datasette 1.0a8 introduces several new plugin hooks, a JavaScript plugin system and moves plugin configuration from metadata.yaml to datasette.yaml. Read more about the release in the annotated release notes for 1.0a8.

Datasette Enrichments is a new feature for Datasette that supports enriching data by running custom code against every selected row in a table. Read Datasette Enrichments: a new plugin framework for augmenting your data for more details, plus a video demo of enrichments for geocoding addresses and processing text and images using GPT-4.

datasette-comments is a new plugin by Alex Garcia which adds collaborative commenting to Datasette. Alex built the plugin for Datasette Cloud, but it's also available as an open source package for people who are hosting their own Datasette instances. See Annotate and explore your data with datasette-comments on the Datasette Cloud blog for more details.

Datasette 1.0a4 has a fix for a security vulnerability in the Datasette 1.0 alpha series: the API explorer interface exposed the names of private databases and tables in public instances that were protected by a plugin such as datasette-auth-passwords, though not the actual content of those tables. See the security advisory for more details and workarounds for if you can't upgrade immediately. The latest edition of the Datasette Newsletter also talks about this issue.

datasette-write-ui: a Datasette plugin for editing, inserting, and deleting rows introduces a new plugin adding add/edit/delete functionality to Datasette, developed by Alex Garcia. Alex built this for Datasette Cloud, and this post is the first announcement made on the new Datasette Cloud blog - see also Welcome to Datasette Cloud.

Datasette 1.0a3 is an alpha release of Datasette that previews the new default JSON API design that’s coming in version 1.0 - the single most significant change planned for that 1.0 release.

New tutorial: Data analysis with SQLite and Python. This tutorial, originally presented at PyCon 2023, includes a 2h45m video and an extensive handout that should be useful with or without the video. Topics covered include Python's sqlite3 module, sqlite-utils, Datasette, Datasette Lite, advanced SQL patterns and more.

I built a ChatGPT plugin to answer questions about data hosted in Datasette describes a new experimental Datasette plugin to enable people to query data hosted in a Datasette interface via ChatGPT, asking human language questions that are automatically converted to SQL and used to generate a readable response.

Using Datasette in GitHub Codespaces is a new tutorial showing how Datasette can be run in GitHub's free Codespaces browser-based development environments, using the new datasette-codespaces plugin.

Examples of sites built using Datasette now includes screenshots of Datasette deployments that illustrate a variety of problems that can be addressed using Datasette and its plugins.

Semantic search answers: Q&A against documentation with GPT3 + OpenAI embeddings shows how Datasette can be used to implement semantic search and build a system for answering questions against an existing corpus of text, using two new plugins: datasette-openai and datasette-faiss, and a new tool: openai-to-sqlite.

Datasette 0.64 is out, and includes a strong warning against running SpatiaLite in production without disabling arbitrary SQL queries, plus a new --setting default_allow_sql off setting to make it easier to do that. See Datasette 0.64, with a warning about SpatiaLite for more about this release. A new tutorial, Building a location to time zone API with SpatiaLite, describes how to safely use SpatiaLite and Datasette to build and deploy an API for looking up time zones for a latitude/longitude location.

This release focuses on performance, in particular against large tables, and introduces some minor breaking changes for CSS styling in Datasette plugins. - Removed the unit conversions feature and its dependency, Pint. This means Datasette is now compatible with the upcoming Python 3.13. (#2400, #2320) - 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) - Fixed a confusing error that occurred if metadata.json contained nested objects. (#2403) - Fixed a bug with ?_trace=1 where it returned a blank page if the response was larger than 256KB. (#2404) - 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) - Fixed a text spacing with table descriptions on the homepage. (#2399) - Performance improvements for large tables: - Suggested facets now only consider the first 1000 rows. (#2406) - Improved performance of date facet suggestion against large tables. (#2407) - Row counts stop at 10,000 rows when listing tables. (#2398) - On table page the count stops at 10,000 rows too, with a "count all" button to execute the full count. (#2408) - New .dicts() internal method on Results that returns a list of dictionaries representing the results from a SQL query: (#2414) python rows = (await db.execute("select * from t")).dicts() - 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) - Similarly, default table styles now only apply to <table class="rows-and-columns">. (#2420)

• More CSS compatibility with future Datasette alpha releases. #21

• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417

• Now skips tables ending in _fts to avoid duplicate search results in most recent Datasette alphas.
• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. #20, datasette#2417

• Database write page URLs are now /db/-/write, the old /-/write?database=db page redirects to the new location. #12
• Removed the application menu item so as not to duplicate the database action item.
• New row action menu item (on Datasette 1.0a13 and higher) linking to a SQL query to edit the current values of that row. #10
• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417

• Fix for compatibility with the base_url setting. Thanks, @meowcat #25
• autocomplete="off" on password field. Thanks, @brandonrobertz #24
• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417

• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417

• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417

• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417

• Fixed CSS for compatibility with upcoming Datasette 1.0 alpha. datasette#2417

• Display errors differently, depending on this new Datasette feature. #8

• Now supports has_* columns in addition to is_* and should_*. #3

• Fixed compatibility issue with datasette-write-ui and datasette-comments. #2

• Initial release. Adds interactive checkbox widgets to any integer column with a is_* or should_* name, provided the current user has update-row permissions. #1

• 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)
• Fixed bug where running Datasette with one or more -s/--setting options could over-ride settings that were present in datasette.yml. (#2389)
• 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)
• Failed CSRF checks now display a more user-friendly error page. (#2390)
• Fixed a bug where the json1 extension was not correctly detected on the /-/versions page. Thanks, Seb Bacon. (#2326)
• Fixed a bug where the Datasette write API did not correctly accept Content-Type: application/json; charset=utf-8. (#2384)
• Fixed a bug where Datasette would fail to start if metadata.yml contained a queries block. (#2386)