releases: 22509033
This data as json
| html_url | id | node_id | tag_name | target_commitish | name | draft | author | prerelease | created_at | published_at | body | repo | reactions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/sqlite-utils/releases/tag/2.0 | 22509033 | MDc6UmVsZWFzZTIyNTA5MDMz | 2.0 | master | 2.0 | 0 | 9599 | 0 | 2019-12-30T06:18:58Z | 2019-12-30T06:26:09Z | 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](https://sqlite-utils.readthedocs.io/en/stable/python-api.html#python-api-upsert) and [Upserting data using the CLI](https://sqlite-utils.readthedocs.io/en/stable/cli.html#upserting-data) 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](https://sqlite-utils.readthedocs.io/en/stable/python-api.html#python-api-insert-replace) and [Insert-replacing data using the CLI](https://sqlite-utils.readthedocs.io/en/stable/cli.html#cli-insert-replace) for more. For full background on this change, see issue #66. | 140912432 |
Links from other tables
- 0 rows from release in assets