2.0.1

The .upsert() and .upsert_all() methods now raise a sqlite_utils.db.PrimaryKeyRequired exception if you call them without specifying the primary key column using pk= (#73).

2.0

This release changes the behaviour of upsert. It’s a breaking change, hence 2.0.

The upsert command-line utility and the .upsert() and .upsert_all() Python API methods have had their behaviour altered. They used to completely replace the affected records: now, they update the specified values on existing records but leave other columns unaffected.

See Upserting data using the Python API and Upserting data using the CLI for full details.

If you want the old behaviour - where records were completely replaced - you can use $ sqlite-utils insert ... --replace on the command-line and .insert(..., replace=True) and .insert_all(..., replace=True) in the Python API. See Insert-replacing data using the Python API and Insert-replacing data using the CLI for more.

For full background on this change, see issue #66.

1.12.1

https://sqlite-utils.readthedocs.io/en/latest/changelog.html#v1-12-1

1.12

https://sqlite-utils.readthedocs.io/en/latest/changelog.html#v1-12

1.11

https://sqlite-utils.readthedocs.io/en/stable/changelog.html#v1-11

1.10

https://sqlite-utils.readthedocs.io/en/stable/changelog.html#v1-10

1.9

https://sqlite-utils.readthedocs.io/en/stable/changelog.html#v1-9

1.8

https://sqlite-utils.readthedocs.io/en/stable/changelog.html#v1-8

1.7.1

https://sqlite-utils.readthedocs.io/en/latest/changelog.html#v1-7-1

1.7

https://sqlite-utils.readthedocs.io/en/latest/changelog.html#v1-7