Bug #60756 Import does not work
Submitted: 5 Apr 2011 6:23 Modified: 16 May 2011 19:05
Reporter: Ivan Petrov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.33 OS:Linux (Ubuntu 10.10 (Maverick Meerkat))
Assigned to: CPU Architecture:Any
Tags: import
Triage: Needs Triage: D2 (Serious)

[5 Apr 2011 6:23] Ivan Petrov 
Description:
10:12:33 Restoring shop (product)
Running: mysql --defaults-extra-file="/tmp/tmpPwLglU/extraparams.cnf"   --protocol=pipe --user=root --socket=/var/run/mysqld/mysqld.sock --default-character-set=utf8 --comments < "/media/data/mysql/shop_product.sql"
ERROR 2047 (HY000): Wrong or unknown protocol

Operation failed with exitcode 1

How to repeat:
Export and then import schema

Suggested fix:
Works without "--protocol=pipe"
[5 Apr 2011 6:25] Ivan Petrov 
MySQL 5.1.49
[5 Apr 2011 6:28] Ivan Petrov 
MySQL Workbench CE for Linux/Unix version 5.2.33
Configuration Directory: /home/ivan/.mysql/workbench
Data Directory: /usr/share/mysql-workbench
Cairo Version: 1.10.0
Rendering Mode: OpenGL is not available on this system, so Native is used for rendering.
OS: Linux 2.6.35-28-generic-pae
CPU: 2x Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz 2000.000 MHz, 3,2 GB RAM
[5 Apr 2011 9:34] Valeriy Kravchuk 
Verified on Ubunut 10.04. As soon as your instance is defined on localhost and connects using socket (NOT TCP/IP), we have this bug. 

See bug #59730 for a similar bug about data export.
[16 May 2011 19:05] Paul Dubois 
Noted in 5.2.34 changelog.

For import and export command operations using a Unix socket file,
Workbench added an incorrect --pipe option to the command.