Hi!
On Nov 16, gshchepa@stripped wrote:
>
> ChangeSet@stripped, 2007-11-16 23:44:55+04:00, gshchepa@stripped +4 -0
> Fixed bug #31677.
> 1. Multi-byte characters was never escaped, because they was always
> skipped before escaping process.
> 2. 8bit escape characters, termination and enclosed characters were
> silently ignored by SELECT INTO query, but LOAD DATA INFILE
> algorithm is 8bit-clear, so data was corrupted during encoding.
no, we won't fix it in 5.0. the dump in 5.0 is a mix of character sets
anyway, we won't fix a case when somebody uses a byte which is a
part of a multi-byte character in one of those character sets as an
ESCAPED BY character.
In 5.1 when you fix 30946 and the dump will be consistently converted
to one charset, this bug will be re-tested.
Regards / Mit vielen Grüssen,
Sergei
--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <serg@stripped>
/ /|_/ / // /\ \/ /_/ / /__ Principal Software Developer
/_/ /_/\_, /___/\___\_\___/ MySQL GmbH, Dachauer Str. 37, D-80335 München
<___/ Geschäftsführer: Kaj Arnö - HRB
München 162140
