MySQL Bugs: #85237: Using Workbench, problem with auto increment

Bug #85237	Using Workbench, problem with auto increment
Submitted:	28 Feb 2017 22:27	Modified:	28 Mar 2017 23:15
Reporter:	chuck snell	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.47 CE	OS:	Windows
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Auto Increment import csv

Description:
Hello,

First I admit I am new to Work Bench but from the forum it was suggested I fill out a bug report.

I am trying to import a csv. I do not have a good (lone) field for a primary key id.

So I created a field for the id and checked AI (auto increment) (also check PK and NN)

I am getting: 
ERROR 1366: Incorrect integer value: '' for column  averaged_historical_forecasts_a_id' at row 1 

SQL Statement: 

here is "a" workbench generated statement: 

INSERT INTO `temperature_forecasts`.`averaged_historical_forecasts_a` (`Read_Date`, `Read_Time`, `Forecast__Date`, `_Forecast_Time_`, `Start_Hour`, `End_Hour`, `Columbia_ACCU-Weather`, `Columbia__NOAA`, `Lewisburg_ACCU-Weather`, `Lewisburg_NOAA`, `Shelbyville_ACCU-Weather`, `Shelbyville_NOAA`, `Manchester_ACCU-Weather`, `Manchester_NOAA`, `Decherd_ACCU-Weather`, `Decherd_NOAA`, `averaged_historical_forecasts_a_id`) VALUES ('2015-02-05', '7:55', '2015-02-05', ' 8:00 - 9:00', ' 8:00', '9:00', '27.5', '26.5', '27.5', '27', '27.5', '28', '27.5', '28', '29.5', '30', ''); 

I would have thought the INSERT statement would not include the id and notice the comma at the end before the closing parentheses. 

I am pretty sure I saw it work one time but I was still setting up things and since I am getting the above error.

How to repeat:
Repeats every time with an attempted import

Thank you for the bug report. Please try version 6.3.9 and comment the result here.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".