Open jpwynn opened 12 years ago
When converting from sqlite3 to postgres, it's possible to have strings in sqlite that are too long for postgres.
Currently, it throws an error and stop running, without even saying which table it was starting, or the record/field that caused the issue.
Best solution IMO would be to truncate the field and continue (with warning message).
Next best solution IMO would be to indicate which table/record/field was too long.
When converting from sqlite3 to postgres, it's possible to have strings in sqlite that are too long for postgres.
Currently, it throws an error and stop running, without even saying which table it was starting, or the record/field that caused the issue.
Best solution IMO would be to truncate the field and continue (with warning message).
Next best solution IMO would be to indicate which table/record/field was too long.