08.12.2017 13:56, Mark Rotteveel wrote:
>> Because you are sending queries in connection charset. And string
>> literals in them are
>> in connection charset. Because of that your 'x' cannot have COLLATE
>> PXW_HUNDC.
>
> I don't agree with this. The string literal is in the connection
>
Unfortunately dump happened to be useless. It confirmed that problem is with
database lock and type of the problem, but that was rather clear from log
records, and unfortunately nothing about the reasons.
As the next step please first of all provide OS info - kernel, libc, gcc and
libstdc++
08.12.2017 11:56, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] wrote:
> I don't agree with this. The string literal is in the connection
> character set, but the value should be converted to the target character
> set (of the column) for the comparison
No. Imagine connection charset
08.12.2017 12:07, Mark Rotteveel m...@lawinegevaar.nl [firebird-support] wrote:
> It should return no results. If it can't transliterate, it means that
> the character definitely does not exist in the target column, so the
> comparison is false.
When character is transliterated into charset
Anyway thank you for your effort.
Do you think the problem might be caused more likely by embedded clients vs.
SuperClient or just by "heavy load"?
(Meanwhile FB3.0 SuperServer runs already two days without any trouble.)
Here are the version numbers but I'm not any linux guru so I hope that's
On 2017-12-08 12:01, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] wrote:
> 08.12.2017 11:56, Mark Rotteveel m...@lawinegevaar.nl
> [firebird-support] wrote:
>> I don't agree with this. The string literal is in the connection
>> character set, but the value should be converted to the
On 2017-12-07 19:06, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] wrote:
> 07.12.2017 18:46, Gabor Boros mlngl...@bgss.hu [firebird-support]
> wrote:
>> Why does the connection charset count?
>
>Because you are sending queries in connection charset. And string
> literals in them
Hi All,
I have a database with default UTF8 character set and UNICODE_CI collation:
CREATE DATABASE 'MYDB' PAGE_SIZE 4096 DEFAULT CHARACTER SET UTF8
COLLATION UNICODE_CI;
Execute the next script:
CREATE COLLATION UNICODE_CI_AS_HU FOR UTF8 FROM UNICODE_CI ACCENT
SENSITIVE 'LOCALE=hu_HU';
