• https://github.com/simonw/sqlite-utils/issues/344#issuecomment-982014776

Make table.transform() preserve STRICT mode.

:books: Documentation preview :books:: https://sqlite-utils--604.org.readthedocs.build/en/604/

https://dev.to/hugovk/help-test-python-312-beta-1508/

:books: Documentation preview :books:: https://sqlite-utils--591.org.readthedocs.build/en/591/

Adds COLUMN_TYPE_MAPPING for TIME fields that are mapped as datetime.timedelta for MySQL and json represantation for datetime.timedelta in order to fix #522

:books: Documentation preview :books:: https://sqlite-utils--596.org.readthedocs.build/en/596/

The issue is that underlying iterator is not fully consumed within the body of the with file_progress() block. Instead, that block creates generator expressions like docs = (dict(zip(headers, row)) for row in reader)

These iterables are consumed later, outside the with file_progress() block, which consumes the underlying iterator, and in turn updates the progress bar.

This means that the ProgressBar.__exit__ method gets called before the last time the ProgressBar.update method gets called. The result is that the code to make the cursor invisible (inside the update() method) is called after the cleanup code to make it visible (in the __exit__ method).

The fix is to move consumption of the docs iterators within the progress bar block. (

(An additional fix, to make ProgressBar more robust against this kind of misuse, would to make it refusing to update after its __exit__ method had been called, just like files cannot be read() after they are closed. That requires a in the click library).

Note that Github diff obscures the simplicity of this diff, it's just indenting a block of code.

:books: Documentation preview :books:: https://sqlite-utils--598.org.readthedocs.build/en/598/

According to both Debian and Ubuntu, the correct “target triple” for arm64 is aarch64-linux-gnu, so we should be looking in /usr/lib/aarch64-linux-gnu for mod_spatialite.so.

I can confirm that on both of my Debian arm64 SBCs, libsqlite3-mod-spatialite installs to that path.

$ ls -l /usr/lib/*/*spatial* lrwxrwxrwx 1 root root 23 Dec 1 2022 /usr/lib/aarch64-linux-gnu/mod_spatialite.so -> mod_spatialite.so.7.1.0 lrwxrwxrwx 1 root root 23 Dec 1 2022 /usr/lib/aarch64-linux-gnu/mod_spatialite.so.7 -> mod_spatialite.so.7.1.0 -rw-r--r-- 1 root root 7348584 Dec 1 2022 /usr/lib/aarch64-linux-gnu/mod_spatialite.so.7.1.0

This is a set of before and after snippets of pytest’s output for this PR.

Before

$ pytest tests/test_get.py ...... [ 73%] tests/test_gis.py ssssssssssss [ 75%] tests/test_hypothesis.py .... [ 75%]

After

$ pytest tests/test_get.py ...... [ 73%] tests/test_gis.py ............ [ 75%] tests/test_hypothesis.py .... [ 75%]

Issue: #599

:books: Documentation preview :books:: https://sqlite-utils--600.org.readthedocs.build/en/600/

Refs: - #592

• [x] Tests against weird shaped tables

I need to test that this works against:

• rowid tables
• Tables that have a column called rowid even though they are not rowid tables

:books: Documentation preview :books:: https://sqlite-utils--593.org.readthedocs.build/en/593/

Refs: - #577

:books: Documentation preview :books:: https://sqlite-utils--584.org.readthedocs.build/en/584/

Just like the Datasette prepare_connection hook, this PR adds a similar hook for the sqlite-utils plugin system.

The sole argument is conn, since I don't believe a database or datasette argument would be relevant here.

I want to do this so I can release sqlite-utils plugins for my SQLite extensions, similar to the Datasette plugins I've release for them.

An example plugin: https://gist.github.com/asg017/d7cdf0d56e2be87efda28cebee27fa3c

```bash $ sqlite-utils install https://gist.github.com/asg017/d7cdf0d56e2be87efda28cebee27fa3c/archive/5f5ad549a40860787629c69ca120a08c32519e99.zip

$ sqlite-utils memory 'select hello("alex") as response' [{"response": "Hello, alex!"}] ``` Refs: - #574

:books: Documentation preview :books:: https://sqlite-utils--573.org.readthedocs.build/en/573/

Refs: - #559

:books: Documentation preview :books:: https://sqlite-utils--560.org.readthedocs.build/en/560/

Refs: - #551

:books: Documentation preview :books:: https://sqlite-utils--553.org.readthedocs.build/en/553/

Refs: - #545

:books: Documentation preview :books:: https://sqlite-utils--549.org.readthedocs.build/en/549/

Refs #544

• [x] Documentation for CLI options
• [x] Documentation for new Python API parameters: most_common: bool and least_common: bool
• [x] Tests for CLI
• [x] Tests for Python API

:books: Documentation preview :books:: https://sqlite-utils--537.org.readthedocs.build/en/537/

Fixes #525. All tests pass.

There's perhaps a better way to name lambdas? There could be a collision if a caller passes a function with name like lambda_123456.

SQLite documentation is a little, ah, lite on function name specs. If there is a character that can be used in place of underscore in a SQLite function name that is not permitted in a Python function identifier then that could be a good way to prevent accidental collisions. (I tried dash, colon, dot, no joy).

Otherwise, there is little chance of this happening and if it should happen the risk is mitigated by now throwing an exception in the case of a (name, arity) collision without replace=True.

:books: Documentation preview :books:: https://sqlite-utils--526.org.readthedocs.build/en/526/

This fixes #514 by making the initial insert for upserts include all columns, so that new rows can be added to tables with non-pkey columns that have constraints.

(aside: I'm not a python programmer. pip? pipenv? venv? These are mystical incantations to me. The process to set up this repo for local development and testing was so easy. Thank you for the excellent contributing documentation!)

:books: Documentation preview :books:: https://sqlite-utils--515.org.readthedocs.build/en/515/

Fixes #509, Fixes #336

Thanks for the great library! I fixed a bug that sqlite-utils transform breaks DEFAULT values. All tests already present passed with no changes, and I added some tests for this PR.

In #509 case, fixed here.

```shell $ sqlite3 test.db << EOF CREATE TABLE mytable ( col1 TEXT DEFAULT 'foo', col2 TEXT DEFAULT (STRFTIME('%Y-%m-%d %H:%M:%f', 'NOW')) ) EOF

$ sqlite3 test.db "SELECT sql FROM sqlite_master WHERE name = 'mytable';" CREATE TABLE mytable ( col1 TEXT DEFAULT 'foo', col2 TEXT DEFAULT (STRFTIME('%Y-%m-%d %H:%M:%f', 'NOW')) )

$ sqlite3 test.db "INSERT INTO mytable DEFAULT VALUES; SELECT * FROM mytable;" foo|2022-12-21 01:15:39.669

$ sqlite-utils transform test.db mytable --rename col1 renamedcol1 $ sqlite3 test.db "SELECT sql FROM sqlite_master WHERE name = 'mytable';" CREATE TABLE "mytable" ( [renamedcol1] TEXT DEFAULT 'foo', [col2] TEXT DEFAULT (STRFTIME('%Y-%m-%d %H:%M:%f', 'NOW')) # ← Non-String Value )

$ sqlite3 test.db "INSERT INTO mytable DEFAULT VALUES; SELECT * FROM mytable;" foo|2022-12-21 01:15:39.669 foo|2022-12-21 01:15:56.432 ```

And #336 case also fixed. Special values are described here.

3.2. The DEFAULT clause ... A default value may also be one of the special case-independent keywords CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP.

```shell $ echo 'create table bar (baz text, created_at timestamp default CURRENT_TIMESTAMP)' | sqlite3 foo.db $ sqlite3 foo.db SQLite version 3.39.5 2022-10-14 20:58:05 Enter ".help" for usage hints. sqlite> .schema bar CREATE TABLE bar (baz text, created_at timestamp default CURRENT_TIMESTAMP); sqlite> .exit

$ sqlite-utils transform foo.db bar --column-order baz $ sqlite3 foo.db SQLite version 3.39.5 2022-10-14 20:58:05 Enter ".help" for usage hints. sqlite> .schema bar CREATE TABLE IF NOT EXISTS "bar" ( [baz] TEXT, [created_at] FLOAT DEFAULT CURRENT_TIMESTAMP ); sqlite> .exit

$ sqlite-utils transform foo.db bar --column-order baz $ sqlite3 foo.db SQLite version 3.39.5 2022-10-14 20:58:05 Enter ".help" for usage hints. sqlite> .schema bar CREATE TABLE IF NOT EXISTS "bar" ( [baz] TEXT, [created_at] FLOAT DEFAULT CURRENT_TIMESTAMP # ← Non-String Value ); ```

:books: Documentation preview :books:: https://sqlite-utils--519.org.readthedocs.build/en/519/

Fixes #527

:books: Documentation preview :books:: https://sqlite-utils--528.org.readthedocs.build/en/528/

Does what it says and nothing else. This is the same set of paths as Datasette uses.

:books: Documentation preview :books:: https://sqlite-utils--536.org.readthedocs.build/en/536/

This also passes in the extension path when specified in GIS methods. Wherever we know an extension path, we use db.init_spatialite(find_spatialite() or load_extension).

:books: Documentation preview :books:: https://sqlite-utils--531.org.readthedocs.build/en/531/

Add support for compound foreign keys, as per issue #117

Not sure if this is the right approach. In particular I'm unsure about:

• the new ForeignKey class, which replaces the namedtuple in order to ensure that column and other_column are forced into tuples. The class does the job, but doesn't feel very elegant.
• I haven't rewritten guess_foreign_table to take account of multiple columns, so it just checks for the first column in the foreign key definition. This isn't ideal.
• I haven't added any ability to the CLI to add compound foreign keys, it's only in the python API at the moment.

The PR also contains a minor related change that columns and tables are always quoted in foreign key definitions.

Hi,

I needed to extract data in JSON Arrays to normalize data imports. I've quickly hacked the following together based on #241 which refers to #239 where you, @simonw, wrote:

Could this handle lists of objects too? That would be pretty amazing - if the column has a [{...}, {...}] list in it could turn that into a many-to-many.

They way this works in my work is that many-to-many relationships are created for anything that maps to an dictionary in a list, and many-to-one relations for everything else (assumed to be scalar values). Not sure what the best approach here would be? Are many-to-one relationships are at all useful here?

What do you think about this approach? I could try to add it to the cli interface and documentation if wanted.

Thanks for this awesome piece of software in any case! :sun_with_face:

closes #507

https://dwheeler.com/essays/fixing-unix-linux-filenames.html

:books: Documentation preview :books:: https://sqlite-utils--508.org.readthedocs.build/en/508/

https://github.com/simonw/sqlite-utils/pull/498

:books: Documentation preview :books:: https://sqlite-utils--499.org.readthedocs.build/en/499/

alternatively, self.disable_fts()

I was wondering why my all my databases were giving wild search results. Turns out create_trigger was not sticking!

Running sqlite-utils triggers x.db shows [] after running enable-fts using the python api. Looking at the counts trigger it seems that is the right way to save triggers. triggers show up now

:books: Documentation preview :books:: https://sqlite-utils--498.org.readthedocs.build/en/498/

:books: Documentation preview :books:: https://sqlite-utils--486.org.readthedocs.build/en/486/

I haven't tested this yet but wanted to get a heads-up whether this kind of change would be useful or if I should just duplicate the function and tweak it within my code

:books: Documentation preview :books:: https://sqlite-utils--480.org.readthedocs.build/en/480/

Work in progress. Still needs documentation and tests (and to cover more cases of things that might have changed).

Refs: - #467

:books: Documentation preview :books:: https://sqlite-utils--468.org.readthedocs.build/en/468/

sqlite "IS" is equivalent to SQL "IS NOT DISTINCT FROM"

closes #423

Refs #470

:books: Documentation preview :books:: https://sqlite-utils--473.org.readthedocs.build/en/473/

Also testing https://docs.readthedocs.io/en/stable/pull-requests.html

Work in progress, partly to test the ReadTheDocs preview link action.

Refs: - #426

:books: Documentation preview :books:: https://readthedocs-preview--460.org.readthedocs.build/en/460/

Read the Docs repository was renamed from readthedocs/readthedocs-preview to readthedocs/actions/. Now, the preview action is under readthedocs/actions/preview and is tagged as v1

:books: Documentation preview :books:: https://sqlite-utils--463.org.readthedocs.build/en/463/

Refs #464

Read the Docs repository was renamed from readthedocs/readthedocs-preview to readthedocs/actions/. Now, the preview action is under readthedocs/actions/preview and is tagged as v1

Also testing fix for: - https://github.com/readthedocs/readthedocs-preview/issues/10

:books: Documentation preview :books:: https://sqlite-utils--462.org.readthedocs.build/en/462/

This PR addresses a feature request raised in issue #449. Specifically this PR adds a functionality that lets users duplicate a table via:

python table_new = db["my_table"].duplicate("new_table")

Test added in file tests/test_duplicate.py.

Happy to make changes to meet maintainers' feedback, if any.

Fixes a typo.

Trying to get this to work with Pyodide.

Refs: https://github.com/simonw/click-default-group-wheel/issues/3

Closes #418

This adds four files to .gitignore:

.hypothesis/
Pipfile
Pipfile.lock
pyproject.toml

Those are all generated in the course of development and testing.

Closes #398

This adds SpatiaLite helpers to the CLI.

```sh

init spatialite when creating a database

sqlite-utils create database.db --enable-wal --init-spatialite

add geometry columns

needs a database, table, geometry column name, type, with optional SRID and not-null

this will throw an error if the table doesn't already exist

sqlite-utils add-geometry-column database.db table-name geometry --srid 4326 --not-null

spatial index an existing table/column

this will throw an error it the table and column don't exist

sqlite-utils create-spatial-index database.db table-name geometry ```

Docs and tests are included.

Refs #79

This PR adds three new Spatialite-related methods to Database and Table:

• Database.init_spatialite loads the Spatialite extension and initializes it
• Table.add_geometry_column adds a geometry column
• Table.create_spatial_index creates a spatial index

Has tests and documentation. Feedback very welcome.

Refs #375

Still needs:

• [x] Refactor @insert_upsert_options so that it doesn't duplicate @import_options
• [x] Tests
• [x] Documentation
• [x] Try it against a really big file

Refs #366

Refs #356

Still TODO:

• [x] Get --lines working, with tests
• [x] Get --text working, with tests
• [x] Get regular JSON import working with --convert with tests
• [x] Get --lines working with --convert with tests
• [x] Get --text working with --convert with tests
• [x] Get --csv and --tsv import working with --convert with tests
• [x] Get --nl working with --convert with tests
• [x] Documentation for all of the above

Refs #346 and #344.

I needed this for a project of mine, and I thought it'd be useful to have it in sqlite-utils (It's also mentioned in #248 ). The current implementation works (data is read & data types are inferred correctly. I've added a single straightforward test case, but @simonw please let me know if there are any non-obvious flags/combinations I should test too.

the library deal with Postgres type jsonb as dictionary, add dict type as a TEXT for mapping to sqlite

While working on updating sqlite-utils for NixOS/Nixpkgs, I came a cross the following:

In 5ec6686153e29ae10d4921a1ad4c841f192f20e2, a new dependency was added on dateutils (https://pypi.org/project/dateutils/).

I believe this is unintentional, and instead python-dateutil (https://pypi.org/project/python-dateutil/) was intended.

My reasoning is: - python-dateutil is imported here in recipes.py - The mypy type-python-dateutil dependency in setup.py - python-dateutil is a dependency of dateutils as seen in the output in docs/tutorial.ipynb

Seems like the trailing "s" seems to be the source of confusion 😅

I've swapped the dependencies out, hope this helps.

It seems that click 8.x uses None as the default value for multiple=True options.

This change makes the code forward-compatible with click 8.x.

See this build failure for more info: https://hydra.nixos.org/build/156926608

This tests against the latest 3.10 RC, https://www.python.org/downloads/release/python-3100rc2/

Refs #319.

Addresses #246 - this is a bit of a kludge because it doesn't actually validate the FTS string, just makes sure that it will not crash when executed, but I figured that building a query parser is a bit out of the scope of sqlite-utils and if you actually want to use the query language, you probably need to parse that yourself.

Refs #311.

Refs #251, #302.

• [x] Get recipes working
• [x] Document recipes
• [x] Implement db[table].convert(...) method
• [x] Add tests for recipes that use the new Python method
• [x] Implement db[table].convert(..., multi=True) mechanism
• [x] Documentation for db[table].convert(...)
• [x] Refactor sqlite-utils convert to use the new method

Refs #272. Initial implementation only does CSV data, still needs:

• [x] Implement --save
• [x] Add --dump to the documentation
• [x] Add --attach example to the documentation
• [x] Replace :memory: in documentation

This appears to be the canonical solution.

Refs #260

The description for create-table was duplicated from create-index.

Remove extra [

Noticed a typo in the docs and followed that up with a spellcheck. Had to bite my tongue at some of the British spellings.

…are escaped aps unicode for lists, tuples, dicts

Fix of #257

Refs #239. Still needs documentation and CLI implementation.

Hi,

I ran into a problem when trying to create a database from my Apple Healthkit data using healthkit-to-sqlite. The program crashed because of an invalid insert statement that was generated for table rDistanceCycling.

The actual problem turned out to be in sqlite-utils. Table.insert_all processes the data to be inserted in chunks of rows and checks for every chunk which columns are used, and it will collect all column names in the variable all_columns. The collection of columns is done using a nested list comprehension that is not completely correct.

I'm using a Windows machine and had to make a few adjustments to the tests in order to be able to run them because they had a posix dependency.

Thanks, kind regards,

Frans

```

this is a (condensed) chunk of data from my Apple healthkit export that caused the problem.

the 3 last items in the chunk have additional keys: metadata_HKMetadataKeySyncVersion and metadata_HKMetadataKeySyncIdentifier

chunk = [{'sourceName': 'AppleÂ\xa0Watch van Frans', 'sourceVersion': '7.0.1', 'device': '<<HKDevice: 0x281cf6c70>, name:Apple Watch, manufacturer:Apple Inc., model:Watch, hardware:Watch3,4, software:7.0.1>', 'unit': 'km', 'creationDate': '2020-10-10 12:29:09 +0100', 'startDate': '2020-10-10 12:29:06 +0100', 'endDate': '2020-10-10 12:29:07 +0100', 'value': '0.00518016'}, {'sourceName': 'AppleÂ\xa0Watch van Frans', 'sourceVersion': '7.0.1', 'device': '<<HKDevice: 0x281cf6c70>, name:Apple Watch, manufacturer:Apple Inc., model:Watch, hardware:Watch3,4, software:7.0.1>', 'unit': 'km', 'creationDate': '2020-10-10 12:29:10 +0100', 'startDate': '2020-10-10 12:29:07 +0100', 'endDate': '2020-10-10 12:29:08 +0100', 'value': '0.00544049'}, {'sourceName': 'AppleÂ\xa0Watch van Frans', 'sourceVersion': '6.2.6', 'device': '<<HKDevice: 0x281cf83e0>, name:Apple Watch, manufacturer:Apple Inc., model:Watch, hardware:Watch3,4, software:6.2.6>', 'unit': 'km', 'creationDate': '2020-10-14 05:54:12 +0100', 'startDate': '2020-07-15 16:40:50 +0100', 'endDate': '2020-07-15 16:42:49 +0100', 'value': '0.952092', 'metadata_HKMetadataKeySyncVersion': '1', 'metadata_HKMetadataKeySyncIdentifier': '3:674DBCDB-3FE8-40D1-9FC1-E54A2B413805:616520450.99823:616520569.99360:119'}, {'sourceName': 'AppleÂ\xa0Watch van Frans', 'sourceVersion': '6.2.6', 'device': '<<HKDevice: 0x281cf83e0>, name:Apple Watch, manufacturer:Apple Inc., model:Watch, hardware:Watch3,4, software:6.2.6>', 'unit': 'km', 'creationDate': '2020-10-14 05:54:12 +0100', 'startDate': '2020-07-15 16:42:49 +0100', 'endDate': '2020-07-15 16:44:51 +0100', 'value': '0.848983', 'metadata_HKMetadataKeySyncVersion': '1', 'metadata_HKMetadataKeySyncIdentifier': '3:674DBCDB-3FE8-40D1-9FC1-E54A2B413805:616520569.99360:616520691.98826:119'}, {'sourceName': 'AppleÂ\xa0Watch van Frans', 'sourceVersion': '6.2.6', 'device': '<<HKDevice: 0x281cf83e0>, name:Apple Watch, manufacturer:Apple Inc., model:Watch, hardware:Watch3,4, software:6.2.6>', 'unit': 'km', 'creationDate': '2020-10-14 05:54:12 +0100', 'startDate': '2020-07-15 16:44:51 +0100', 'endDate': '2020-07-15 16:46:50 +0100', 'value': '0.834403', 'metadata_HKMetadataKeySyncVersion': '1', 'metadata_HKMetadataKeySyncIdentifier': '3:674DBCDB-3FE8-40D1-9FC1-E54A2B413805:616520691.98826:616520810.98305:119'}]

def all_columns_old(): all_columns = [col for col in chunk[0]] all_columns += [column for record in chunk for column in record if column not in all_columns] return all_columns

def all_columns_new(): all_columns = [col for col in chunk[0]] for record in chunk: all_columns += [column for column in record if column not in all_columns] return all_columns

if name == 'main': from pprint import pprint

print('problem: ')
pprint(all_columns_old())
print('\nfix: ')
pprint(all_columns_new())

```

Refs #232

The limit can be passed as a string to the query builder to have an offset. I have tested it using the shorthand limit=f"15, 30", the standard syntax should work too.

Refs #207

• [x] Improve design of CLI output
• [x] Truncate long values in least/most common
• [x] Add a -c column selection option
• [x] Tests
• [x] Documentation

Refs #192. Still needs tests.

Refs #173

I was playing around with sqlite-utils, creating a Roam Research dogsheep-style importer for Datasette, and ran into a slight snag.

I wanted to use a generator to add an order column in an importer. It looked something like:

``` def order_generator(iterable, attr=None): if attr is None: attr = "order" order: int = 0

for i in iterable:
    i[attr] = order
    order += 1
    yield i

```

When I used this with insert_all and other things, it worked fine--but it didn't work as the records argument to m2m. I dug into it, and sqlite-utils is explicitly checking if the records argument is a list or a tuple. I flipped the check upside down, and now it checks if the argument is a mapping. If it's a mapping, it wraps it in a list, otherwise it leaves it alone.

(I get that it might not really make sense to put the order column on the second table. I changed my import schema a bit, and no longer have a real example, but maybe this change still makes sense.)

The automated tests still pass, but I did not add any new ones.

Let me know what you think! I'm really loving Datasette and its ecosystem; thanks for everything!

The sqlite-utils insert releases.db releases - --pk is missing the pk field name, added "id" to fix it.

Takes my test down from ten minutes to four seconds. Refs #172.

Refs #114

• [x] Ability to change the primary key
• [x] Support for changing default value for columns
• [x] Support for changing NOT NULL status of columns
• [x] Support for copying existing foreign keys and removing them
• <strike>Support for conversions= parameter</strike>
• [x] Detailed documentation
• [x] PRAGMA foreign_keys stuff

Refs #165

One of these is my fault, and the other is one I just happened to come across. They're harmless, but might as well be fixed.

Addresses #145.

I think this should do the job. If it meets with your approval I'll update this PR to include an update to the documentation -- I came across this bug while preparing a PR to update the documentation around batch_size in any event.

Refs #150. Needs tests and documentation, including for the new db.execute() and db.executescript() methods.

Closes #139.

Deletes all rows in the table (if it exists) before inserting new rows. SQLite doesn't implement a TRUNCATE TABLE statement but does optimize an unqualified DELETE FROM.

This can be handy if you want to refresh the entire contents of a table but a) don't have a PK (so can't use --replace), b) don't want the table to disappear (even briefly) for other connections, and c) have to handle records that used to exist being deleted.

Ideally the replacement of rows would appear instantaneous to other connections by putting the DELETE + INSERT in a transaction, but this is very difficult without breaking other code as the current transaction handling is inconsistent and non-systematic. There exists the possibility for the DELETE to succeed but the INSERT to fail, leaving an empty table. This is not much worse, however, than the current possibility of one chunked INSERT succeeding and being committed while the next chunked INSERT fails, leaving a partially complete operation.

See commit messages for details. I ran into this while investigating another feature/issue.

Add type conversion for Panda's Timestamp, if Panda library is present in system (thanks for this project, I was about to do the same thing from scratch)

I need this for geojson-to-sqlite, in particular https://github.com/simonw/geojson-to-sqlite/issues/6

Also exclude 'tests' from runtime installation.

Refs #66

This adds the option for a user to set up triggers in the database to keep their FTS table in sync with the parent table.

Ref: https://sqlite.org/fts5.html#external_content_and_contentless_tables

I would prefer to make the creation of triggers the default behavior, but that will break existing usage where people have been calling populate_fts after inserting new rows.

I am happy to make changes to the PR as you see fit.

Closes #59

The table names weren't escaped using double quotes in the populate_fts method.

Reproducible case: ```

import sqlite_utils db = sqlite_utils.Database("abc.db") db["http://example.com"].insert_all([ ... {"id": 1, "age": 4, "name": "Cleo"}, ... {"id": 2, "age": 2, "name": "Pancakes"} ... ], pk="id")

See #54

• [x] table.insert({"name": "Barry"}).m2m("tags", lookup={"tag": "Coworker"})
• [x] Explicit table name .m2m("humans", ..., m2m_table="relationships")
• [x] Automatically use an existing m2m table if a single obvious candidate exists (a table with two foreign keys in the correct directions)
• [x] Require the explicit m2m_table= argument if multiple candidates for the m2m table exist
• [x] Documentation

Refs #23

Refs #35

Still to do:

• [x] Unit tests
• [x] Switch to using .get()
• [x] Better exceptions, plus unit tests for what happens if pk does not exist
• [x] Documentation
• [x] Ensure compound primary keys work properly
• [x] alter=True support