You are telling me that in my example the index unicode_ci_ai of two
varchar(10) don't fit in a 8K page but with Unicode fit ? What page size do
you recommend ?
A segunda, 15/10/2018, 20:14, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] escreveu:
> 15.10.2018 15:00, Luis Forra luis.fo
I found that if I add the a extra field in the index like the pk and make
the index unique it works fine. Is expected to work fine even with the bug
that you refer ?
A segunda, 15/10/2018, 22:53, hv...@users.sourceforge.net
[firebird-support] escreveu:
>
>
> The problem is that multy-level co
You are telling me that in my example the index unicode_ci_ai of two
varchar(10) don't fit in a 8K page but with Unicode fit ? What page size do
you recommend ?
A segunda, 15/10/2018, 20:14, Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] escreveu:
> 15.10.2018 15:00, Luis Forra luis.fo
I found that if I add the a extra field in the index like the pk and make
the index unique it works fine. Is expected to work fine even with the bug
that you refer ?
A segunda, 15/10/2018, 22:53, hv...@users.sourceforge.net
[firebird-support] escreveu:
>
>
> The problem is that multy-level co
The problem is that multy-level collations can't be used for full match in
indices.
If you need details, search fb-devel for thread "UNICODE case/accent
insensitive bugs" started at 10 Jun 2009.
See also CORE-2457
As a workaround, you might try to use two single-segment indices
15.10.2018 15:00, Luis Forra luis.fo...@gmail.com [firebird-support] wrote:
> What I'm doing wrong ?
CI AI indexes are much bigger because of ICU implementation of index key
derivation.
You must increase page size of your database to return index depth to norm.
--
WBR, SD.
---
I'm out of the office till the 18th of October with a limited access to my
emails.
With the best wishes,
Georgiy Kovalov
