Releases · simonw/sqlite-chronicle

If you delete a record and then insert a new record that reuses the same primary keys the __added_ms recorded for that new record will now record when it was re-created, not when the original was created. #24

Can now be run using sqlite-chronicle, or without first installing it using uvx sqlite-chronicle. #23
New sqlite-chronicle --version flag.
Improved --help output and README.

INSERT OR REPLACE INTO now works correctly. #20
Switched to [dependency-groups] for dev dependencies, so uv run pytest now runs the tests against a fresh checkout.
New utility functions disable_chronicle(), is_chronicle_enabled(), and list_chronicled_tables(). #18
CLI tool for disabling chronicle: python -m sqlite_chronicle db.sqlite table --disable.

New upgrade_chronicle(conn, table_name) function for upgrading from older chronicle versions. #17
README now includes an example of the chronicle SQL schema. #16

AFTER UPDATE trigger now detects if the row data has not changed and avoids incrementing the version and __updated_ms if that is the case. #10
New naming convention for columns on the chronicle table: added_ms, updated_ms, version, deleted are now __added_ms, __updated_ms, __version, __deleted.
New CLI mechanism: python -m sqlite_chronicle data.db table1 table2 to enable chronicle for the specified tables. #8
Noted that INSERT OR REPLACE INTO ... will trigger a version bump even if the row data has not changed. Recommend using INSERT INTO ... ON CONFLICT to avoid this problem. #7

Fix for a bug where enable_chronicle() failed with an error if the table did not have a column called id. #5

New updates_since() function for looping through updates that have occurred since a specific version. #2
The version is now incremented for any change to any row, which ensures the system can handle cases where more than 1,000 rows are inserted or updated simultaneously. #3

Releases: simonw/sqlite-chronicle