Re: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-17 Thread Luis Forra luis.fo...@gmail.com [firebird-support]
hv...@users.sourceforge.net [firebird-support] < firebird-support@yahoogroups.com> escreveu no dia terça, 16/10/2018 à(s) 08:19: > > > ---In firebird-support@yahoogroups.com, wrote : > > > I found that if I add the a extra field in the index like the pk and > make the index unique it works

Re: Re: Fwd: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-17 Thread g...@liconic.com [firebird-support]
I'm out of the office till the 18th of October with a limited access to my emails. With the best wishes, Georgiy Kovalov

Re: Fwd: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-17 Thread Luis Forra luis.fo...@gmail.com [firebird-support]
nonomura nono181...@yahoo.co.jp [firebird-support] < firebird-support@yahoogroups.com> escreveu no dia terça, 16/10/2018 à(s) 15:14: > > > Analitico and all, > > I found that if I add the a extra field in the index like the pk and make > the index unique it works fine. > > > Many of those

Re: Fwd: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-16 Thread hv...@users.sourceforge.net [firebird-support]
> Many of those collation problems seem to relate to unicode_ci and > unicode_ci_ai, > and this relates to the usage of ICU functions. > > FB seems to set collation strength properly only where it relates to unique > index. > Otherwise the strength is left default, i.e. equivalent of collate

Re: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-16 Thread Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
On 16-10-2018 09:16, hv...@users.sourceforge.net [firebird-support] wrote: > PS your messages is duplicated in this list, fix it please That is more likely Yahoo Groups messing up again, this occasionally causes messages to be sent multiple times (or not at all), and I have a suspicion that it

Re: Fwd: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-16 Thread nonomura nono181...@yahoo.co.jp [firebird-support]
Analitico and all, I found that if I add the a extra field in the index like the pk and make the index unique it works fine. Many of those collation problems seem to relate to unicode_ci and unicode_ci_ai, and this relates to the usage of ICU functions. FB seems to set collation strength

Re: Re: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-16 Thread g...@liconic.com [firebird-support]
I'm out of the office till the 18th of October with a limited access to my emails. With the best wishes, Georgiy Kovalov

Re: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-16 Thread hv...@users.sourceforge.net [firebird-support]
---In firebird-support@yahoogroups.com, wrote : > I found that if I add the a extra field in the index like the pk and make > the index unique it works fine. Ok. > Is expected to work fine even with the bug that you refer ? Not sure what is "fine" here. In any case -

Fwd: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-15 Thread Analitico analitic...@gmail.com [firebird-support]
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

Re: [firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-15 Thread Luis Forra luis.fo...@gmail.com [firebird-support]
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

[firebird-support] Re: Firebird 3.0.4 unicode_ci_ai index problems

2018-10-15 Thread hv...@users.sourceforge.net [firebird-support]
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