This was a weird bug to run into. Basically I changed a CharField into
a ForeignKey field and ran `makemigrations` to get the job done.
However, rather than doing a `RemoveField` and an `AddField`, migrations
created a single `AlterField` which worked just fine in SQLite, but blew
up in PostgreSQL with:
psycopg2.ProgrammingError: operator class "varchar_pattern_ops" does
not accept data type integer
The fix was to rewrite the single migration into the two separate steps.
MariaDB/MySQL doesn't handle indexes on TextFields well and for some
reason, Django's migrations opts to blow up rather than handle this in a
more user-friendly way. The fix here isn't ideal, but should be
sufficient should anyone try to use Paperless with MySQL.
Rename exporter to export and fixt some debugging
Account for files not matching the sender/title pattern
Added a safety note
Wrong regex on the name parser
Renamed the command to something slightly less ambiguous
