select * from rdb$triggers where rdb$trigger_source like 'CHECK%' [CORE1539]

[firebird-automations]

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

[firebird-automations]

Commented by: Alexander Markevich (gs_alexander)

DataBase

[firebird-automations]

Modified by: Alexander Markevich (gs_alexander)

Attachment: ETALON.rar [ 10630 ]

[firebird-automations]

Commented by: @asfernandes

There is [WIN1251?] characters in system fields.

You should read release notes section about metadata upgrade script to fix it.

[firebird-automations]

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

[firebird-automations]

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.

[firebird-automations]

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).

[firebird-automations]

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.

[firebird-automations]

Commented by: @asfernandes

Verifying the viability to implement correct direct match or just disable for now.

[firebird-automations]

Modified by: @asfernandes

status: Resolved [ 5 ] => Reopened [ 4 ]

resolution: Won't Fix [ 2 ] =>

[firebird-automations]

Commented by: @asfernandes

That's a old problem, but in the past the error may be hidden with wrong results instead of exceptions.

[firebird-automations]

Modified by: @asfernandes

Version: 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 ]

[firebird-automations]

Modified by: @asfernandes

status: Reopened [ 4 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 RC1 [ 10201 ]

[firebird-automations]

Modified by: @pcisar

Link: This issue is related to QA197 [ QA197 ]

[firebird-automations]

Modified by: @pcisar

Workflow: jira [ 13347 ] => Firebird [ 14026 ]

[firebird-automations]

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: Done successfully

[firebird-automations]

Commented by: @pcisar

Test created.

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]