When using the hash-algorithm "blowfish" in saltedpasswords
the hash is 60 chars long - therefore the field length has
been set to 60 characters in SQL, too.
Actually when converting old MD5 passwords to salted
copies, an additional identifer char (M or C) is added to
the hash which results in a 61 character hash.
The result is that login is not possible anymore after
converting the passwords like suggested by the reports
module - the database field has to be increased.
To be safe and because varchar only takes as much space
as really needed increase the field length to 100 chars.
Note for Updating: You do not need to run DB compare
after updating. Everything will work fine without, as
well as after the DB compare. The BulkUpdater, which
needs this change because additionally checks this
and requests a DB compare.