• Gleb Shchepa's avatar
    Bug# 30946: mysqldump silently ignores --default-character-set · e642140b
    Gleb Shchepa authored
                when used with --tab
    
    1) New syntax: added CHARACTER SET clause to the
      SELECT ... INTO OUTFILE (to complement the same clause in
      LOAD DATA INFILE).
      mysqldump is updated to use this in --tab mode.
    
    2) ESCAPED BY/ENCLOSED BY field parameters are documented as
       accepting CHAR argument, however SELECT .. INTO OUTFILE
       silently ignored rests of multisymbol arguments.
       For the symmetrical behavior with LOAD DATA INFILE the
       server has been modified to fail with the same error:
    
         ERROR 42000: Field separator argument is not what is
                      expected; check the manual
    
    3) Current LOAD DATA INFILE recognizes field/line separators
       "as is" without converting from client charset to data
       file charset. So, it is supposed, that input file of
       LOAD DATA INFILE consists of data in one charset and
       separators in other charset. For the compatibility with
       that [buggy] behaviour SELECT INTO OUTFILE implementation
       has been saved "as is" too, but the new warning message
       has been added:
    
         Non-ASCII separator arguments are not fully supported
    
       This message warns on field/line separators that contain
       non-ASCII symbols.
    e642140b
sql_class.h 95.6 KB