Releases · simonw/sqlite-chronicle

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

Provide feedback