I got the problem when using mysqldump -T --default-character-set=utf8 with some binary(16) fields that had some binary data inside. I can now see that the Range.txt files created by mysqldump just don't have the binary fields! It does work without the default-character-set option, but this seems dangerous if used over different systems.
$ sudo mysqldump -T . test --default-character-set=UTF8 Range > Range.sql $ sudo mysqlimport --default-character-set=utf8 test /tmp/Range.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690131 Title: mysqlimport fails on table names which are keywords if unescaped -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
