Git-history

- Fixed bug where the item table did not correctly link to the commits using a foreign key. [59](https://github.com/simonw/git-history/issues/59)
- Fixed bug where some repositories would not process correctly due to data from older versions not being successfully loaded from the commit history. [64](https://github.com/simonw/git-history/issues/64)

- Fixed bug where databases containing multiple file histories created using the `--namespace` option could have later commits applied to them in subsequent runs. [42](https://github.com/simonw/git-history/issues/42), [#43](https://github.com/simonw/git-history/issues/43)

- Fixed critical bug where columns were incorrectly recorded as consistently toggling between null and their current value. [33](https://github.com/simonw/git-history/issues/33)
- Documentation now includes links to live examples of databases created using this tool. [30](https://github.com/simonw/git-history/issues/30)
- `--wal` option for turning on SQLite WAL mode - useful if you want to safely run queries against the database file while it is still being built. [31](https://github.com/simonw/git-history/issues/31)
- Fixed bug where list and dict values were not correctly compared for equality. [32](https://github.com/simonw/git-history/issues/32)
- The `item_version_detail` SQL view now includes a `_changed_column` JSON array of column names that changed in each version. [37](https://github.com/simonw/git-history/issues/37)
- Nested packages such as `--import xml.etree.ElementTree` can now be imported. [39](https://github.com/simonw/git-history/issues/39)
- `item_version._item` is now an indexed column. [38](https://github.com/simonw/git-history/issues/38)

- The `item_version` table now only records values that have changed since the previous item version. A new `item_changed` many-to-many table records exactly which columns were changed in which item version, to compensate for ambiguous `null` values. [21](https://github.com/simonw/git-history/issues/21)
- New `--full-versions` option for storing full copies of each version instead of storing just the columns that have changed.
- Major backwards-incompatible schema changes - see README for details of the new schema.
- New `--dialect` option for specifying a CSV dialect if you don't want to use auto-detection. [27](https://github.com/simonw/git-history/issues/27)
- The history for multiple files can now be stored in the same database, using the new `--namespace` option. [13](https://github.com/simonw/git-history/issues/13)
- `--skip HASH`, `--start-at HASH` and `--start-after HASH` options for skipping specific Git commits or starting processing at or after a specific hash. [26](https://github.com/simonw/git-history/issues/26), [#28](https://github.com/simonw/git-history/issues/28)

- Major changes to the database schema. Foreign keys now use integer primary key IDs rather than using lengthy item or commit hashes, which reduces the database size for large repositories by almost half. [12](https://github.com/simonw/git-history/issues/12)
- Python generators can now be used in `--convert` functions. [16](https://github.com/simonw/git-history/issues/16)
- Reserved columns are now marked by an underscore prefix, for example `_id` and `_commit`. [14](https://github.com/simonw/git-history/issues/14)

- Fixed bug where files with a `"rowid"` column would fail to import correctly. [10](https://github.com/simonw/git-history/issues/10)