Geoff Worboys [email protected] [firebird-support] wrote: > Mark Rotteveel [email protected] [firebird-support] wrote: >> I think this is a bug and it should be reported as such. If >> there is no uppercase equivalent of a character in the current >> character set, then UPPER() should use the character itself, >> not throw a transliteration error.
> I tend to agree, but wasn't certain whether it was intentional. > It is easily tested on these SBCS (which is how I am now > confident that this was the only character with the problem in > WIN1252), so it seemed possible that it might be by design. > I will report it and let the developers decide. No I won't. Someone beat me to it (in September). I should have thought to search the tracker before posting here, I only searched my forum archives. http://tracker.firebirdsql.org/browse/CORE-4546 I've added a comment since I was there anyway. -- Geoff Worboys Telesis Computing Pty Ltd
