v2.1.0

• New imdb column ordering on the crew table.
  Should not break anything for queries specifying which columns to return. For select * from crew type queries, this will affect the number of columns returned, as there is now one more than previously.

v2.0.0

Fix leading to Breaking change:

• Wrong db datatype for Rating value (integer when they should have been decimals)

Non breaking fix:

• Partial TSV download not fetching missing files (e.g. aborted download being re-run).

The invalid datatype is nasty because:

1. has been there since day one, and on github for 8 years with zero remarks about this problem.
2. risks breaking some workflow, especially delta workflows that require consistent types (e.g. insert into, select from variants that would have issues with incompatible column types). This potential risk requires a breaking change announcement (major release bump), even if 99% of uses won't notice the difference, assuming most people rebuild the entire DB from scratch most of the time.

Full Changelog: 1.2.0...2.0.0

v1.2.0

• New option --only "table(s)" which allows for importing a subset of tables only

This option can cut the DB size significantly. See the updated readme section "Disk space tips" for more info about how much, and the typical trade-offs this option brings.

v1.1.0

• New flag for skipping index creation

This flag cuts the DB size in half approximately, but it also means joining columns will be unusably slow. That is unless you create your own indices manually. See readme for the rationale.

v1.0.1

• Performance improvement that affect joining tables.
• The index creation step now provides a progress bar.

Note, an additional index was introduced on people to make the README example orders of magnitude faster. The downside is that this index takes up some additional space.

v1.0.0

Stable release 🎉

5 years in pre-release is enough.

Changes:

• Fix spelling of column episodes
  Note: This is a breaking change in case you depended on the typo (eposides).
  Closes #3
• Readme updated with schema diagram and query examples
  Note: foreign key constraints are not defined nor enforced, even though depicted in the diagram. Foreign keys are not used, as a safe-guard against bad data from IMDB that may violate the constraints. Better to get whatever data IMDB offers into the DB than be picky about relations enforcement.
  Closes #2

v0.1.5

Fixes:

• Invalid data type used for ID schemas (integers where they should have been strings)
• Null (\N) characters not replaced with DB nulls. Happened when the imdb null-characters occurred in the last column of a TSV file.