Hello.
Add --hex-blob to mysqldump command line options. Adam Lipscombe wrote: > Folks > > > I am trialling MySQL 5 before we all upgrade, however others need to = > import=20 > my dump files into their existing MySQL4.x databases > > MySQL 5 mysqldump seems exports BIT fields as true =3D '=01', false =3D = > '\0'. > > When that dump file is imported into MySQL 4 these value are not=20 > interpreted correctly. MySQL4.x does not have a real BIT type , rather = > it=20 > uses TINYINT(1). > Both '=01' and '\0' seem to be interpreted as "false", and the relevant = > > TINYINT(1) field is set to 0. > > So far that has meant that I have to hand-edit my dump file to convert = > '=01'=20 > to 1, '\0' to 0. > > Does anyone know a way around this? > > > > TIA - Adam Lipscombe > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
