On May 20, Timothy P Clark wrote:
> > records_in_range is meant to ask how many keys there is between two
> > different keys.
> > There shouldn't be a different answer if the user would ask for
> > 'LIKE "ABC%"' or BETWEEN "ABC\0" AND "ABC\FF"
> My original post probably wasn't clear, but it's the second format
> that is giving us trouble. In some cases, that \FF (i.e.
> max_sort_char) is not a valid (i.e. convertable) character for a given
> character set (e.g. cp932), and this causes DB2 to complain when the
> \FF comes through records_in_range.
Just trying to clarify.
Are you saying that for LIKE "ABC%" you get "ABC\FF" in
records_in_range() even in character sets where \FF is not a valid
If yes - it must be a bug, both range ends must be valid strings in
their character set.
Or is the problem in different definitions of cp932 in MySQL and DB2 ?
Regards / Mit vielen Grüßen,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <serg@stripped>
/ /|_/ / // /\ \/ /_/ / /__ Principal Software Engineer/Server Architect
/_/ /_/\_, /___/\___\_\___/ Sun Microsystems GmbH, HRB München 161028
<___/ Sonnenallee 1, 85551 Kirchheim-Heimstetten
Geschäftsführer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Häring