Bug #78550 Append Data - Warnings about incompatible data types do not appear anymore

Submitted: 25 Sep 2015 6:18 Modified: 22 Oct 2015 21:27
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.4 OS:Any
Assigned to: CPU Architecture:Any

[25 Sep 2015 6:18] Javier Treviño
Description:
In the Append Data dialog, whenever a column from the source (upper) grid is drag and dropped into another column on the target (lower) grid, a check for data types compatibility was run in previous versions, but it is not happening on the current 1.3.4 version.

For example when attempting to map a source column of data type varchar to a target column of data type integer, a warning should appear stating that the data types are incompatible.

How to repeat:
1. Open MySQL for Excel
2. Open a connection to a MySQL server, select a schema and a table
3. Import the contents of any table that contains columns of different data types.
4. Select 1 or more rows of the imported data
5. Click Append Excel Data to Table
6. Select Manual from the mapping method combo
7. Drag a source column of one data type to a target column of a different data type (for example source = varchar, target = integer)
8. NOTE a warning stating the data types are incompatible should have appeared but there is none. Also the cells of the source column should have been colored red (indicating there is a warning associated to that column).
[22 Oct 2015 21:27] Philip Olson
Fixed as of the upcoming MySQL for Excel 1.3.5 release, and here's the changelog entry:

Attempting to save data to a column where the data can not be written
(incompatible data type) now generates an error.

Thank you for the bug report.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.049 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.