id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,pull_request,body,repo,type,active_lock_reason,performed_via_github_app,reactions,draft,state_reason
1855885427,I_kwDOBm6k_c5unpBz,2143,De-tangling Metadata before Datasette 1.0,15178711,open,0,,,24,2023-08-18T00:51:50Z,2023-08-24T18:28:27Z,,CONTRIBUTOR,,"Metadata in Datasette is a really powerful feature, but is a bit difficult to work with. It was initially a way to add ""metadata"" about your ""data"" in Datasette instances, like descriptions for databases/tables/columns, titles, source URLs, licenses, etc. But it later became the go-to spot for other Datasette features that have nothing to do with metadata, like permissions/plugins/canned queries. 

Specifically, I've found the following problems when working with Datasette metadata:

1. Metadata cannot be updated without re-starting the entire Datasette instance.
2. The `metadata.json`/`metadata.yaml` has become a kitchen sink of unrelated (imo) features like plugin config, authentication config, canned queries
3. The Python APIs for defining extra metadata are a bit awkward (the `datasette.metadata()` class, `get_metadata()` hook, etc.)

## Possible solutions

Here's a few ideas of Datasette core changes we can make to address these problems. 

### Re-vamp the Datasette Python metadata APIs

The Datasette object has a single `datasette.metadata()` method that's a bit difficult to work with. There's also no Python API for inserted new metadata, so plugins have to rely on the `get_metadata()` hook.

The `get_metadata()` hook can also be improved - it doesn't work with async functions yet, so you're quite limited to what you can do.

(I'm a bit fuzzy on what to actually do here, but I imagine it'll be very small breaking changes to a few Python methods)

### Add an optional `datasette_metadata` table

Datasette should detect and use metadata stored in a new special table called `datasette_metadata`. This would be a regular table that a user can edit on their own, and would serve as a ""live updating"" source of metadata, than can be changed while the Datasette instance is running.

Not too sure what the schema would look like, but I'd imagine:

```sql
CREATE TABLE datasette_metadata(
  level text,
  target any,
  key text,
  value any,
  primary key (level, target)
)
```

Every row in this table would map to a single metadata ""entry"".

- `level` would be one of ""datasette"", ""database"", ""table"", ""column"", which is the ""level"" the entry describes. For example, `level=""table""` means it is metadata about a specific table, `level=""database""` for a specific database, or `level=""datasette""` for the entire Datasette instance.
- `target` would ""point"" to the specific object the entry metadata is about, and would depend on what `level` is specific. 
  - `level=""database""`: `target` would be the string name of the database that the metadata entry is about. ex `""fixtures""`
  - `level=""table""`: `target` would be a JSON array of two strings. The first element would be the database name, and the second would be the table name. ex `[""fixtures"", ""students""]`
  - `level=""column""`: `target` would be a JSON array of 3 strings: The database name, table name, and column name. Ex `[""fixtures"", ""students"", ""student_id""`]
- `key` would be the type of metadata entry the row has, similar to the current ""keys"" that exist in `metadata.json`. Ex `""about_url""`, `""source""`, `""description""`, etc
- `value` would be the text value of be metadata entry. The literal text value of a description, about_url, column_label, etc

A quick sample:

level | target | key | value
-- | -- | -- | --
datasette | NULL | title | my datasette title...
db | fixtures | source | <description of my database source>
table | [""fixtures"", ""students""] | label_column | student_name
column | [""fixtures"", ""students"", ""birthdate""] | description | <description of the fixtures.students.birthdate column>

This `datasette_metadata` would be configured with other tools, and hopefully not manually by end users. Datasette Core could also offer a UI for editing entries in `datasette_metadata`, to update descriptions/columns on the fly.

### Re-vamp `metadata.json` and move non-metadata config to another place

The motivation behind this is that it's awkward that `metadata.json` contains config about things that are not strictly metadata, including:

- Plugin configuration
- [Authentication/permissions](https://docs.datasette.io/en/latest/authentication.html#access-permissions-in-metadata) (ex the `allow` key on datasettes/databases/tables
- Canned queries. might be controversial, but in my mind, canned queries are application-specific code and configuration, and don't describe the data that exists in SQLite databases. 

I think we should move these outside of `metadata.json` and into a different file. The `datasette.json` idea in  #2093 may be a good solution here: plugin/permissions/canned queries can be defined in `datasette.json`, while `metadata.json`/`datasette_metadata` will strictly be about documenting databases/tables/columns. 
",107914493,issue,,,"{""url"": ""https://api.github.com/repos/simonw/datasette/issues/2143/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,
1857234285,I_kwDOBm6k_c5usyVt,2145,If a row has a primary key of `null` various things break,9599,open,0,,,23,2023-08-18T20:06:28Z,2023-08-21T17:30:01Z,,OWNER,,"Stumbled across this while experimenting with `datasette-write-ui`. The error I got was a 500 on the `/db` page:

> `'NoneType' object has no attribute 'encode'`

Tracked it down to this code, which assembles the URL for a row page:

https://github.com/simonw/datasette/blob/943df09dcca93c3b9861b8c96277a01320db8662/datasette/utils/__init__.py#L120-L134

That's because `tilde_encode` can't handle `None`: https://github.com/simonw/datasette/blob/943df09dcca93c3b9861b8c96277a01320db8662/datasette/utils/__init__.py#L1175-L1178

",107914493,issue,,,"{""url"": ""https://api.github.com/repos/simonw/datasette/issues/2145/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,
1856760386,PR_kwDOBm6k_c5YQGcc,2144,Bump the python-packages group with 3 updates,49699333,closed,0,,,2,2023-08-18T13:49:37Z,2023-08-21T13:48:18Z,2023-08-21T13:48:16Z,CONTRIBUTOR,simonw/datasette/pulls/2144,"Bumps the python-packages group with 3 updates: [sphinx](https://github.com/sphinx-doc/sphinx), [furo](https://github.com/pradyunsg/furo) and [blacken-docs](https://github.com/asottile/blacken-docs).

Updates `sphinx` from 7.1.2 to 7.2.2
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href=""https://github.com/sphinx-doc/sphinx/releases"">sphinx's releases</a>.</em></p>
<blockquote>
<h2>Sphinx 7.2.2</h2>
<p>Changelog: <a href=""https://www.sphinx-doc.org/en/master/changes.html"">https://www.sphinx-doc.org/en/master/changes.html</a></p>
<h2>Sphinx 7.2.1</h2>
<p>Changelog: <a href=""https://www.sphinx-doc.org/en/master/changes.html"">https://www.sphinx-doc.org/en/master/changes.html</a></p>
<h2>Sphinx 7.2.0</h2>
<p>Changelog: <a href=""https://www.sphinx-doc.org/en/master/changes.html"">https://www.sphinx-doc.org/en/master/changes.html</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href=""https://github.com/sphinx-doc/sphinx/blob/master/CHANGES"">sphinx's changelog</a>.</em></p>
<blockquote>
<h1>Release 7.2.2 (released Aug 17, 2023)</h1>
<h2>Bugs fixed</h2>
<ul>
<li>Fix the signature of the <code>StateMachine.insert_input()</code> patch,
for when calling with keyword arguments.</li>
<li>Fixed membership testing (<code>in</code>) for the :py:class:<code>str</code> interface
of the asset classes (<code>_CascadingStyleSheet</code> and <code>_JavaScript</code>),
which several extensions relied upon.</li>
<li>Fixed a type error in <code>SingleFileHTMLBuilder._get_local_toctree</code>,
<code>includehidden</code> may be passed as a string or a boolean.</li>
<li>Fix <code>:noindex:</code> for <code>PyModule</code> and JSModule``.</li>
</ul>
<h1>Release 7.2.1 (released Aug 17, 2023)</h1>
<h2>Bugs fixed</h2>
<ul>
<li>Restored the the :py:class:<code>str</code> interface of the asset classes
(<code>_CascadingStyleSheet</code> and <code>_JavaScript</code>), which several extensions relied upon.
This will be removed in Sphinx 9.</li>
<li>Restored calls to <code>Builder.add_{css,js}_file()</code>,
which several extensions relied upon.</li>
<li>Restored the private API <code>TocTree.get_toctree_ancestors()</code>,
which several extensions relied upon.</li>
</ul>
<h1>Release 7.2.0 (released Aug 17, 2023)</h1>
<h2>Dependencies</h2>
<ul>
<li><a href=""https://redirect.github.com/sphinx-doc/sphinx/issues/11511"">#11511</a>: Drop Python 3.8 support.</li>
<li><a href=""https://redirect.github.com/sphinx-doc/sphinx/issues/11576"">#11576</a>: Require Pygments 2.14 or later.</li>
</ul>
<h2>Deprecated</h2>
<ul>
<li><a href=""https://redirect.github.com/sphinx-doc/sphinx/issues/11512"">#11512</a>: Deprecate <code>sphinx.util.md5</code> and <code>sphinx.util.sha1</code>.
Use <code>hashlib</code> instead.</li>
<li><a href=""https://redirect.github.com/sphinx-doc/sphinx/issues/11526"">#11526</a>: Deprecate <code>sphinx.testing.path</code>.
Use <code>os.path</code> or <code>pathlib</code> instead.</li>
<li><a href=""https://redirect.github.com/sphinx-doc/sphinx/issues/11528"">#11528</a>: Deprecate <code>sphinx.util.split_index_msg</code> and <code>sphinx.util.split_into</code>.
Use <code>sphinx.util.index_entries.split_index_msg</code> instead.</li>
<li>Deprecate <code>sphinx.builders.html.Stylesheet</code>
and <code>sphinx.builders.html.Javascript</code>.
Use <code>sphinx.application.Sphinx.add_css_file()</code></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/ed84d63e6f2c4fd43b97fc43ee8be4156a13af9e""><code>ed84d63</code></a> Bump to 7.2.2 final</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/ea4a73e148022244bba027b86a8c2bf7067e97be""><code>ea4a73e</code></a> [bot]: Update message catalogues (<a href=""https://redirect.github.com/sphinx-doc/sphinx/issues/11612"">#11612</a>)</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/e47846a812f09ae2ca9e0444ed227934c2eb9c6e""><code>e47846a</code></a> Fix <code>:noindex:</code> for <code>PyModule</code> and JSModule``</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/b2fc47fe3dd0adba46edbb21ef03102ecb997f89""><code>b2fc47f</code></a> Add CHANGES entry for renaming the <code>StateMachine.insert_input()</code> parameter</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/0835c3e8ea6b23fb12b29d9c5104e06595f400b6""><code>0835c3e</code></a> Fix regression in <code>SingleFileHTMLBuilder._get_local_toctree</code></li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/49dc0dd3999f66f27728b974394585422f10d947""><code>49dc0dd</code></a> Fix asset class string interface membership testing</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/8512855776ddd4790547d7e46ad98fd3ee48c2fb""><code>8512855</code></a> Fix signature of docutils include_source monkeypatch (<a href=""https://redirect.github.com/sphinx-doc/sphinx/issues/11610"">#11610</a>)</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/e1d9068c60b43cf8dcb8dbd62ba26900eb63ff3b""><code>e1d9068</code></a> Bump version</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/441a9e4d622e5f00f9fed8f59b9cac251cff9f80""><code>441a9e4</code></a> Bump to 7.2.1 final</li>
<li><a href=""https://github.com/sphinx-doc/sphinx/commit/ec3185373044c120298501dbe91444bdb6ccb04c""><code>ec31853</code></a> Restore <code>TocTree.get_toctree_ancestors()</code></li>
<li>Additional commits viewable in <a href=""https://github.com/sphinx-doc/sphinx/compare/v7.1.2...v7.2.2"">compare view</a></li>
</ul>
</details>
<br />

Updates `furo` from 2023.7.26 to 2023.8.17
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href=""https://github.com/pradyunsg/furo/blob/main/docs/changelog.md"">furo's changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<!-- raw HTML omitted -->
<h2>2023.08.17 -- Wonderous White</h2>
<ul>
<li>Fix compatiblity with Sphinx 7.2.0 and 7.2.1.</li>
</ul>
<h2>2023.07.26 -- Vigilant Volt</h2>
<ul>
<li>Fix compatiblity with Sphinx 7.1.</li>
<li>Improve how content overflow is handled.</li>
<li>Improve how literal blocks containing inline code are handled.</li>
</ul>
<h2>2023.05.20 -- Unassuming Ultramarine</h2>
<ul>
<li>✨ Add support for Sphinx 7.</li>
<li>Drop support for Sphinx 5.</li>
<li>Improve the screen-reader label for sidebar collapse.</li>
<li>Make it easier to create derived themes from Furo.</li>
<li>Bump all JS dependencies (NodeJS and npm packages).</li>
</ul>
<h2>2023.03.27 -- Tasty Tangerine</h2>
<ul>
<li>Regenerate with newer version of sphinx-theme-builder, to fix RECORD hashes.</li>
<li>Add missing class to Font Awesome examples</li>
</ul>
<h2>2023.03.23 -- Sassy Saffron</h2>
<ul>
<li>Update Python version classifiers.</li>
<li>Increase the icon size in mobile header.</li>
<li>Increase admonition title bg opacity.</li>
<li>Change the default API background to transparent.</li>
<li>Transition the API background change.</li>
<li>Remove the &quot;indent&quot; of API entries which have a background.</li>
<li>Break long inline code literals.</li>
</ul>
<h2>2022.12.07 -- Reverent Raspberry</h2>
<ul>
<li>✨ Add support for Sphinx 6.</li>
<li>✨ Improve footnote presentation with docutils 0.18+.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href=""https://github.com/pradyunsg/furo/commit/99f4e6df480ac3d043c09d472acd69390f47e402""><code>99f4e6d</code></a> Prepare release: 2023.08.17</li>
<li><a href=""https://github.com/pradyunsg/furo/commit/59ad807bc6f8c8b36bf5a0bad2609e7781d8aaf9""><code>59ad807</code></a> Update changelog</li>
<li><a href=""https://github.com/pradyunsg/furo/commit/9b94420776972613c3990a31467855ceceefcff7""><code>9b94420</code></a> Accomodate for Sphinx 7.2 behavior change</li>
<li><a href=""https://github.com/pradyunsg/furo/commit/7aeb6d204f808ae0b0da8a5dee6f6035d9cd04cf""><code>7aeb6d2</code></a> [pre-commit.ci] pre-commit autoupdate (<a href=""https://redirect.github.com/pradyunsg/furo/issues/675"">#675</a>)</li>
<li><a href=""https://github.com/pradyunsg/furo/commit/0c9be3f65d6ae84ff56d7679b7d650323b355be3""><code>0c9be3f</code></a> Back to development</li>
<li>See full diff in <a href=""https://github.com/pradyunsg/furo/compare/2023.07.26...2023.08.17"">compare view</a></li>
</ul>
</details>
<br />

Updates `blacken-docs` from 1.15.0 to 1.16.0
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href=""https://github.com/adamchainz/blacken-docs/blob/main/CHANGELOG.rst"">blacken-docs's changelog</a>.</em></p>
<blockquote>
<h2>1.16.0 (2023-08-16)</h2>
<ul>
<li>
<p>Allow Markdown fence options.</p>
<p>Thanks to initial work from Matthew Anderson in <code>PR [#246](https://github.com/asottile/blacken-docs/issues/246) &lt;https://github.com/adamchainz/blacken-docs/pull/246&gt;</code>__.</p>
</li>
<li>
<p>Expand Markdown detection to all Python language names from Pygments: <code>py</code>, <code>sage</code>, <code>python3</code>, <code>py3</code>, and <code>numpy</code>.</p>
</li>
<li>
<p>Preserve leading whitespace lines in reStructuredText code blocks.</p>
<p>Thanks to Julianus Pfeuffer for the report in <code>Issue [#217](https://github.com/asottile/blacken-docs/issues/217) &lt;https://github.com/adamchainz/blacken-docs/issues/217&gt;</code>__.</p>
</li>
<li>
<p>Use exit code 2 to indicate errors from Black, whilst exit code 1 remains for “files have been formatted”.</p>
<p>Thanks to Julianus Pfeuffer for the report in <code>Issue [#218](https://github.com/asottile/blacken-docs/issues/218) &lt;https://github.com/adamchainz/blacken-docs/issues/218&gt;</code>__.</p>
</li>
<li>
<p>Support passing the <code>--preview</code> option through to Black, to select the future style.</p>
</li>
<li>
<p>Remove <code>language_version</code> from <code>.pre-commit-hooks.yaml</code>.
This change allows <code>default_language_version</code> in ``.pre-commit-config.yaml` to take precedence.</p>
<p>Thanks to Aneesh Agrawal in <code>PR [#258](https://github.com/asottile/blacken-docs/issues/258) &lt;https://github.com/adamchainz/blacken-docs/pull/258&gt;</code>__.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/960ead214cd1184149d366c6d27ca6c369ce46b6""><code>960ead2</code></a> Version 1.16.0</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/8f0ed18ce69d35e7e631d2b01983ecf8248667a0""><code>8f0ed18</code></a> Support passing --preview through to Black (<a href=""https://redirect.github.com/asottile/blacken-docs/issues/273"">#273</a>)</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/4eb4e4cdbff31cde3d9ffdd7693d5b7dce4dc506""><code>4eb4e4c</code></a> Tweak changelog note</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/6c7450cfa90581b482d71b451b2d007361aa47c1""><code>6c7450c</code></a> Use exit code 2 to indicate errors (<a href=""https://redirect.github.com/asottile/blacken-docs/issues/272"">#272</a>)</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/99dfc8d0b402b9b7b0f0e723fc1d030063249eac""><code>99dfc8d</code></a> Preserve leading whitespace lines in rST (<a href=""https://redirect.github.com/asottile/blacken-docs/issues/271"">#271</a>)</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/94465e83e7253b4caef1e00fcb30b74ced33f08e""><code>94465e8</code></a> Reformat markdown tests with dedent() (<a href=""https://redirect.github.com/asottile/blacken-docs/issues/270"">#270</a>)</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/7cd5f30f0f9e014bda566a1893df3b9c7f9a2c48""><code>7cd5f30</code></a> Use .md in glob example</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/f97e56994178e079ab807cebe54c2044f7b2ae55""><code>f97e569</code></a> Document applying to many files (<a href=""https://redirect.github.com/asottile/blacken-docs/issues/269"">#269</a>)</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/ae612b095b5005eee8c3ab9fe65a248d7654582d""><code>ae612b0</code></a> Expand Markdown detection to all Python language names (<a href=""https://redirect.github.com/asottile/blacken-docs/issues/268"">#268</a>)</li>
<li><a href=""https://github.com/adamchainz/blacken-docs/commit/da9b4557afc9b820c40b8d6bdb8f515c6cdec0f5""><code>da9b455</code></a> Replace NamedTuple with plain class (<a href=""https://redirect.github.com/asottile/blacken-docs/issues/267"">#267</a>)</li>
<li>Additional commits viewable in <a href=""https://github.com/asottile/blacken-docs/compare/1.15.0...1.16.0"">compare view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name> dependency` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name> dependency` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions


</details>

<!-- readthedocs-preview datasette start -->
----
:books: Documentation preview :books:: https://datasette--2144.org.readthedocs.build/en/2144/

<!-- readthedocs-preview datasette end -->",107914493,pull,,,"{""url"": ""https://api.github.com/repos/simonw/datasette/issues/2144/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",0,
1856075668,I_kwDOCGYnMM5uoXeU,586,.transform() fails to drop column if table is part of a view,9599,open,0,,,3,2023-08-18T05:25:22Z,2023-08-18T06:13:47Z,,OWNER,,"I got this error trying to drop a column from a table that was part of a SQL view:

> error in view plugins: no such table: main.pypi_releases

Upon further investigation I found that this pattern seemed to fix it:
```python
def transform_the_table(conn):
    # Run this in a transaction:
    with conn:
        # We have to read all the views first, because we need to drop and recreate them
        db = sqlite_utils.Database(conn)
        views = {v.name: v.schema for v in db.views if table.lower() in v.schema.lower()}
        for view in views.keys():
            db[view].drop()
        db[table].transform(
            types=types,
            rename=rename,
            drop=drop,
            column_order=[p[0] for p in order_pairs],
        )
        # Now recreate the views
        for name, schema in views.items():
            db.create_view(name, schema)
```
So grab a copy of any view that might reference this table, start a transaction, drop those views, run the transform, recreate the views again.

> I wonder if this should become an option in `sqlite-utils`? Maybe a `recreate_views=True` argument for `table.tranform(...)`? Should it be opt-in or opt-out?

_Originally posted by @simonw in https://github.com/simonw/datasette-edit-schema/issues/35#issuecomment-1683370548_
            ",140912432,issue,,,"{""url"": ""https://api.github.com/repos/simonw/sqlite-utils/issues/586/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,
1855894222,I_kwDOCGYnMM5unrLO,585,CLI equivalents to `transform(add_foreign_keys=)`,9599,closed,0,,,7,2023-08-18T01:07:15Z,2023-08-18T01:51:16Z,2023-08-18T01:51:15Z,OWNER,,"The new options added in:
- #577
Deserve consideration in the CLI as well.

https://github.com/simonw/sqlite-utils/blob/d2bcdc00c6ecc01a6e8135e775ffdb87572b802b/sqlite_utils/db.py#L1706-L1708",140912432,issue,,,"{""url"": ""https://api.github.com/repos/simonw/sqlite-utils/issues/585/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed