Issue Details (XML | Word | Printable)

Key: CORE-1539
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Adriano dos Santos Fernandes
Reporter: Alexander Markevich
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Firebird Core

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

Created: 25/Oct/07 04:36 PM   Updated: 29/Dec/07 06:23 AM
Component/s: Charsets/Collation
Affects Version/s: 2.0.0, 2.0.1, 2.1 Alpha 1, 2.1 Beta 1, 2.0.2, 2.0.3, 2.1 Beta 2
Fix Version/s: 2.1 RC1

Time Tracking:
Not Specified

File Attachments: 1. File ETALON.rar (67 kB)

Issue Links:
Relate
 


 Description  « Hide
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

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Alexander Markevich added a comment - 25/Oct/07 04:36 PM
DataBase

Adriano dos Santos Fernandes added a comment - 25/Oct/07 05:20 PM
There is [WIN1251?] characters in system fields.

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

Alexander Markevich added a comment - 26/Oct/07 04:32 AM
Yes there is win1251 characters. But rdb$check_metadata procedure doesn't raise an exception on this database. Please comment this situation.

Dmitry Yemanov added a comment - 26/Oct/07 05:38 AM
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).

Alexander Markevich added a comment - 26/Oct/07 07:14 AM
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.

Adriano dos Santos Fernandes added a comment - 26/Oct/07 11:26 AM
Verifying the viability to implement correct direct match or just disable for now.

Adriano dos Santos Fernandes added a comment - 26/Oct/07 11:28 AM
That's a old problem, but in the past the error may be hidden with wrong results instead of exceptions.