MySQL Bugs: #73712: Data type inconsistencies between Varchar (old) and VarChar (new)

Bug #73712	Data type inconsistencies between Varchar (old) and VarChar (new)
Submitted:	25 Aug 2014 16:03	Modified:	10 Oct 2014 0:51
Reporter:	Javier Treviño	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL for Windows: MySQL for Excel	Severity:	S3 (Non-critical)
Version:	1.3.0	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
In MySQL for Excel 1.3.0. along with the feature to show all MySQL data types in the Data Type combo box of the Export Data dialog, the Varchar type was renamed to VarChar to be consistent with the VarBinary type. After that change some internal inconsistencies matching or comparing the Varchar and VarChar types was introduced.

That problem causes glitches in how the VarChar type is displayed in the combo box, so when the detection takes place it is displayed as Varchar but after jumping between columns it is reverted to VarChar.

Also problems in the Append Data dialog to match column types may be introduced with that inconsistency.

How to repeat:
1. Open MySQL for Excel
2. Select some data for export that contains text columns
3. Click on Export Data to New Table
4. On the Export Data dialog navigate through the columns by clicking on the preview grid and notice how the data type is shown sometimes as Varchar and other times as VarChar.

Posted by developer:
 
Changed all references of the Varchar string to VarChar in the code for consistency with the renaming done in 1.3.0.

Posted by developer:
 
Fixed as of the upcoming MySQL for Excel 1.3.3 release, and here's the changelog entry:

For consistency, all references to "Varchar" were changed to "VarChar".

Thank you for the bug report.