Claude d6753a9f57 upsert() now requires a value for every primary key column ... A record missing a primary key value - or with None for one - can never match an existing row, because a NULL primary key never satisfies ON CONFLICT. Such records were previously inserted as brand new rows (silently, for multi-record upsert_all calls) or triggered a KeyError after the insert had already happened. Both cases, including upserting an empty record, now raise PrimaryKeyRequired before any SQL is executed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UnLnhsH25Nnv7LHhekUfPd		2026-07-04 18:43:37 +00:00
..
__init__.py	New migrations system, ported from sqlite-migrate (#754)	2026-06-21 09:40:21 -07:00
__main__.py	Support 'python -m sqlite_utils', closes #368	2022-01-08 18:33:22 -08:00
cli.py	drop-table and drop-view now refuse to drop the wrong object type	2026-07-04 18:13:50 +00:00
db.py	upsert() now requires a value for every primary key column	2026-07-04 18:43:37 +00:00
hookspecs.py	More type annotations (#697)	2025-12-16 22:11:47 -08:00
migrations.py	Run each migration inside a transaction	2026-07-04 18:06:06 +00:00
plugins.py	fix: Plugins are still loaded when running tests (#719)	2026-06-21 16:14:45 -07:00
py.typed	py.typed file so mypy picks up the types, closes #331	2021-11-14 15:21:04 -08:00
recipes.py	More type annotations (#697)	2025-12-16 22:11:47 -08:00
utils.py	Test against Python 3.15-dev, bump ty and Black (#738)	2026-05-17 16:52:48 -07:00