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
String values in error messages are not converted to connection charset [CORE2431] #2847
Comments
Modified by: @dyemanovsummary: Constraint names in eror messages are not converted to connection charset => Constraint names in error messages are not converted to connection charset |
Modified by: @aafemtdescription: If constraint name contains non-ascii characters, it seems to be in UNICODE_FSS in error messages, regardless of connection charset. => String values in error messages aren't converted to connection charset. It includes (at least) constraint names and exception texts. summary: Constraint names in error messages are not converted to connection charset => String values in error messages are not converted to connection charset |
Modified by: @dyemanovassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Commented by: @pcisar Test created. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @aafemt
Is related to QA544
String values in error messages aren't converted to connection charset. It includes (at least) constraint names and exception texts.
Commits: 7a78601
The text was updated successfully, but these errors were encountered: