Skip to content
New issue

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

Log fieldname in write error bad row #9

Open
peel opened this issue Nov 23, 2020 · 2 comments
Open

Log fieldname in write error bad row #9

peel opened this issue Nov 23, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@peel
Copy link

peel commented Nov 23, 2020

Currently the error message contains error cause that does not include field name.
For example:

Failed StatementExecution: ERROR: value too long for type character varying(36) 

The message should include field name, like so:

Failed StatementExecution: ERROR: value too long for type character varying(36) in {{fieldname}}
@peel peel added the enhancement New feature or request label Nov 23, 2020
@chuwy
Copy link
Contributor

chuwy commented Nov 23, 2020

Does this particullar error also happen because we don't have ALTER TABLE statement when maxLength gets increased?

@peel
Copy link
Author

peel commented Nov 23, 2020

TBH I haven't looked at this particular instance as it happened in a third-party setup, but it is very plausible this is the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants