-
-
Notifications
You must be signed in to change notification settings - Fork 233
select * from rdb$triggers where rdb$trigger_source like 'CHECK%' [CORE1539] #1957
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
Comments
Commented by: Alexander Markevich (gs_alexander) DataBase |
Modified by: Alexander Markevich (gs_alexander)Attachment: ETALON.rar [ 10630 ] |
Commented by: @asfernandes There is [WIN1251?] characters in system fields. You should read release notes section about metadata upgrade script to fix it. |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] assignee: Adriano dos Santos Fernandes [ asfernandes ] |
Commented by: Alexander Markevich (gs_alexander) Yes there is win1251 characters. But rdb$check_metadata procedure doesn't raise an exception on this database. Please comment this situation. |
Commented by: @dyemanov The problematic blobs are transliterated into cp1251 correctly, as well as they can be uppercased successfully, so I doubt anything is wrong with the metadata upgrade script. The bug disappears if I allocate buffer via buffer.getBuffer(blob->blb_length) for nod_like even if TEXTTYPE_DIRECT_MATCH flag is set (the same logic as for nod_contains). |
Commented by: Alexander Markevich (gs_alexander) OK. What do we need to do? We have many bases with the same problem and we want to migrate from YA and FB2.0 to FB2.1. |
Commented by: @asfernandes Verifying the viability to implement correct direct match or just disable for now. |
Commented by: @asfernandes That's a old problem, but in the past the error may be hidden with wrong results instead of exceptions. |
Modified by: @asfernandesVersion: 2.0.3 [ 10200 ] Version: 2.0.2 [ 10130 ] Version: 2.1 Beta 1 [ 10141 ] Version: 2.1 Alpha 1 [ 10150 ] Version: 2.0.1 [ 10090 ] Version: 2.0.0 [ 10091 ] |
Modified by: @asfernandesstatus: Reopened [ 4 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 RC1 [ 10201 ] |
Modified by: @pcisarWorkflow: jira [ 13347 ] => Firebird [ 14026 ] |
Commented by: @pcisar Test created. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Alexander Markevich (gs_alexander)
Is related to QA197
Attachments:
ETALON.rar
select * from rdb$triggers where rdb$trigger_source like 'CHECK%'
arithmetic exception, numeric overflow, or string truncation.
Cannot transliterate character between character sets.
But,
select * from rdb$triggers where rdb$trigger_source starting 'CHECK' is work
Commits: a1c1df5
The text was updated successfully, but these errors were encountered: