We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: