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
Bug with COMPUTED BY fields [CORE1286] #1707
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 Beta 1 [ 10141 ] |
Modified by: @asfernandesVersion: 2.0.1 [ 10090 ] Version: 2.0.0 [ 10091 ] Fix Version: 2.0.2 [ 10130 ] |
Commented by: @pcisar Fix verified for 2.1 Beta 1, test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 12230 ] => Firebird [ 15585 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Submitted by: Alexander Tyutik (tut)
Is related to QA143
I have DB with all character fields of UTF8 charset. I've connected to DB with UTF8 charset and tried to add computed field to existing table:
1) ALTER TABLE "Test" ADD STR1 COMPUTED BY ('BLA-BLA-BLA');
After this i've got next error when tried to read table's data: "Arithmetic exception, numeric overflow or string truncation"
2) ALTER TABLE "Test" ADD STR2 COMPUTED BY (_UTF8 'BLA-BLA-BLA');
First time server crashes with "Terminated abnormally" in log file. After server restarted field wass successfully created, but when i tried to read records i've got same error as above.
Commits: 7c3f506 b63bbb7
The text was updated successfully, but these errors were encountered: