You are right but there are other aspects. If I pull a record, change someone's middle initial, then update the record; do I want a ' 4' to be corrected to a canonical '4'? Will all the other programs using my CSV file approve?
There That is an argument for least change.
When one tightens up on type handling, little problems start popping up. Often they keep popping up.
Incidentally, the test changed: SQL_INTEGER() and &SQL_INTEGER can differ semantically.