From efeba1f18c5688c4dcf152da6e9fa0ec2d4bfb34 Mon Sep 17 00:00:00 2001 From: Simon Willison Date: Thu, 8 May 2025 20:00:00 -0700 Subject: [PATCH] Prior to sqlite-utils 4.0 Refs https://github.com/simonw/sqlite-utils/issues/652#issuecomment-2864945717 --- docs/python-api.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/python-api.rst b/docs/python-api.rst index 6893e1c..2e81fa3 100644 --- a/docs/python-api.rst +++ b/docs/python-api.rst @@ -932,7 +932,7 @@ An ``upsert_all()`` method is also available, which behaves like ``insert_all()` 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: