remote/sqlite-utils
1
0
Fork 0
mirror of https://github.com/simonw/sqlite-utils.git synced 2026-09-15 13:04:10 +02:00
Code Issues Projects Releases Packages Wiki Activity

Prior to sqlite-utils 4.0

Browse source 
Refs https://github.com/simonw/sqlite-utils/issues/652#issuecomment-2864945717
This commit is contained in:
Simon Willison 2025-05-08 20:00:00 -07:00
commit efeba1f18c
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/python-api.rst
View file

@ -932,7 +932,7 @@ An ``upsert_all()`` method is also available, which behaves like ``insert_all()`
Alternative upserts using INSERT OR IGNORE Alternative upserts using INSERT OR IGNORE
------------------------------------------ ------------------------------------------
Upserts use ``INSERT INTO ... ON CONFLICT SET``. Prior to ``sqlite-utils 3.x`` (TODO: fill in version) these used a sequence of ``INSERT OR IGNORE`` followed by an ``UPDATE``. This older method is still used for SQLite 3.23.1 and earlier. You can force the older implementation by passing ``use_old_upsert=True`` to the ``Database()`` constructor. Upserts use ``INSERT INTO ... ON CONFLICT SET``. Prior to ``sqlite-utils 4.0`` these used a sequence of ``INSERT OR IGNORE`` followed by an ``UPDATE``. This older method is still used for SQLite 3.23.1 and earlier. You can force the older implementation by passing ``use_old_upsert=True`` to the ``Database()`` constructor.
.. _python_api_convert: .. _python_api_convert: