Bug #15693 Explicitly say that --hex-blob works for BIT fields as well
Submitted: 12 Dec 2005 20:08 Modified: 13 Dec 2005 18:51
Reporter: Gleb Paharenko Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0 OS:Any (all)
Assigned to: Paul DuBois CPU Architecture:Any

[12 Dec 2005 20:08] Gleb Paharenko
Description:
Pleasee explicitly note that --hex-blob works for BIT fields as well, and you can tell that this is
very helpful when importing MySQL 5.0 tables with BIT columns into older releases.

How to repeat:
http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html

"The affected columns are BINARY, VARBINARY, BLOB."

/bin/mysqldump --defaults-file=my.cnf --hex-blob test btt >res 

-- MySQL dump 10.10
--
-- Host: localhost    Database: test
-- ------------------------------------------------------
-- Server version       5.0.16-debug-log

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0
*/;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

--
-- Table structure for table `btt`
--

DROP TABLE IF EXISTS `btt`;
CREATE TABLE `btt` (
  `a` bit(1) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin2;

--
-- Dumping data for table `btt`
--

/*!40000 ALTER TABLE `btt` DISABLE KEYS */;
LOCK TABLES `btt` WRITE;
INSERT INTO `btt` VALUES (0x01),(0x00),(0x01),(0x00);
UNLOCK TABLES;
/*!40000 ALTER TABLE `btt` ENABLE KEYS */;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;

Compare the produced insert statement without --hex-blob

INSERT INTO `btt` VALUES ('^A'),('\0'),('^A'),('\0');

Suggested fix:
Just document this
[12 Dec 2005 20:31] MySQL Verification Team
Thank you for the bug report.
[13 Dec 2005 18:51] Paul DuBois
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

The change occurred in 5.0.13.