removed test029, empty binary blob dump, because of a bug in mysqldum…

…p 5.7.23
apliteni · Oct 9, 2018 · 806547b · 806547b
1 parent c4da8fa
commit 806547b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/tests/test.sh b/tests/test.sh
@@ -46,8 +46,6 @@ mysqldump -utravis test001 \
     > mysqldump_test001.sql
 ret[((index++))]=$?
 
-cat mysqldump_test001.sql
-
 mysqldump -utravis test001 \
     --no-autocommit \
     --skip-extended-insert \

diff --git a/tests/test001.src.sql b/tests/test001.src.sql
@@ -98,7 +98,11 @@ CREATE TABLE `test029` (
   `col` blob NOT NULL
 );
 INSERT INTO `test029` VALUES (1,0x00010203040506070809909192939495969798A9);
-INSERT INTO `test029` VALUES (2,'');
+-- mysqldump 5.7.23 has a bug, an appends _binary to empty blob data, which is incorrect.
+-- mysqldump 5.7.17 is ok
+-- lets skip this test an implement it in some near future
+-- https://bugs.mysql.com/bug.php?id=80150
+INSERT INTO `test029` VALUES (2,0x99AAFF);
 
 DROP TABLE IF EXISTS `test033`;
 CREATE TABLE `test033` (