Bug #74514 Cant import into table with no Primary Key
Submitted: 22 Oct 2014 20:42 Modified: 27 Mar 2015 1:33
Reporter: Craig Macdonald Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2, 6.1 OS:Any (verified on Windows, Mac)
Assigned to: CPU Architecture:Any
Tags: import

[22 Oct 2014 20:42] Craig Macdonald
Description:
If a table has no primary key, the Import button is missing above the results grid. I can still add data to the table manually, e.g. using INSERT INTO.

Ok, I know that primary keys /should/ be there, but if I can add data to a table, why can't I import data using workbench?

How to repeat:
Create a table without a primary key, e.g. equivalent to
CREATE TABLE table1(id INT);

Right click on table on left-hand-side scheme explorer tree, and select "Select Rows - Limit 1000".

Only an Export button is visible in the toolbar of the Results Grid.

Do same for a table with a primary key
CREATE TABLE table2(id INT PRIMARY KEY);

The Results Grid will have more buttons, including Import, Edit Current Row, Delete Selected Row.

This is inconsistent.

Suggested fix:
Don't use existence of primary key to check if a result set can be edited or not?
[23 Oct 2014 11:25] Miguel Solorzano
Thank you for the bug report.
[19 Mar 2015 10:15] Liu ƒ  Yan ƒ‚ ‚¬
Hi, workbench-6.3.2-rc still has this bug, please fix it
[27 Mar 2015 1:33] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.3 release, and here's the changelog entry:

Data could not be imported into a result set when the results did not
contain a Primary Key. The new import wizard does not have this
limitation.

Thank you for the bug report.