Bug #75342 Export Data - wrong number of exporting rows in SQL script dialog
Submitted: 30 Dec 2014 18:09 Modified: 25 Feb 2015 2:21
Reporter: Javier Treviño Email Updates:
Status: Closed Impact on me:
Category:MySQL for Windows: MySQL for Excel Severity:S3 (Non-critical)
Version:1.3.3 OS:Any
Assigned to: CPU Architecture:Any

[30 Dec 2014 18:09] Javier Treviño
When the "Preview SQL statements before they are sent to the server" option is checked in the Global Options dialog, some information is displayed just above the SQL script indicating the number of rows involved in INSERT, DELETE and UPDATE operations. During an Export Data operation, the number of inserting rows is displaying 1 row less than the correct number of rows. This behavior seems to happen only if the "First Row Contains Column Names" in the Export Data dialog is checked.

This is merely cosmetic and does not affect the actual number of exported rows, nor the informational message displayed after the operation takes place which correctly displays the number of processed rows.

How to repeat:
1. Open MySQL for Excel
2. Select a MySQL Schema, within the DB Objects Selection panel click the "Options" button
3. Make sure the "Preview SQL statements before they are sent to the server" option is checked
4. Select some data in an Excel worksheet for Export
5. Click "Export Data to a New Table"
6. Click "Export"
7. In the "Review SQL Script" dialog just above the SQL statements note the informational message reports a number of "inserting" rows and that the number is wrong (#rows - 1).
[7 Jan 2015 1:11] Javier Treviño
Posted by developer:
Fixed the informational label displaying the number of "inserting" rows during an Export Data operation. Before the fix the number was off by 1, only when the "First row contains column names" option was checked.
[25 Feb 2015 2:21] Philip Olson
Posted by developer:
Fixed as of the upcoming MySQL Excel 1.3.4 release, and here's the changelog entry:

Executing "Export Data to a New Table" with the "Preview SQL statements
before they are sent to the server" option enabled would report an
incorrect (off by -1) number of affected rows under the "Review SQL
Script" dialog.

Thank you for the bug report.